bastian Hahn
Greg Hazel
Nicholas Heath
Xiuqiang Jiang
Azat Khuzhin
Volker Lendecke
Catalin Patulea
Patrick Pelletier
Dan Petro
Nate Rosenblum
Gyepi Sam
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
be, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
Hi
I need to clarify my understanding of how bufferevent objects work with
mulithreaded code. If a bufferevent triggers a callback (read or write)
does it hold a lock until that callback completes? Do the locks use a
recursive mutex?
Thanks
ice and terse for inclusion in the
manual, that would rock.) Let us know if it still doesn't make sense
or doesn't work for you though.
peace,
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
at the filter callback has a "enum bufferevent_flush_mode
> state" parameter. Is this relevant here?
>
> Thanks,
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
x" from
https://github.com/nmathewson/libevent/ .
Alternatively, you could wait for 2.1.3-alpha, which I hope will be
out pretty soon.
best wishes,
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsub
probably be a better stress
test than the simple test software I posted before.
Thanks,
-John
From: Nick Mathewson
To: libevent-us...@freehaven.net; John
Sent: Thursday, April 25, 2013 11:36 AM
Subject: Re: [Libevent-users] Simple question about multithreading SSL
bevent 2.1.x-alpha released over this weekend.
best wishes,
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
against libevent 2.0.
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
o unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
)
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
I got symbol not found error on event_base_foreach_event.
Has it been dropped?
Thanks,
Pritesh
27;t really understand
what I didn't realize it yesterday. :)
--
Kind regards,
Jan Danielsson
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
t called recursively by
libevent-openssl.
Any clue on what happened?
Thanks in advance.
Jiaqiang
*******
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
functions as well, but I'm guessing the method
> would be the same regardless). How is this done?
>
> --
> Kind regards,
> Jan Danielsson
>
>
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ntcb(). But the client never prints "Write!".
>
> Rather than use a writecb(), I tried calling bufferevent_write() just
> after the bufferevent_socket_connect(), but the data didn't reach the
> server, which I found to be slig
;s clear I've misunderstood something pretty fundamental about
bufferevents .. but what?
--
Kind regards,
Jan Danielsson
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
re are probably other good approaches too.
best wishes,
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
Hello,
I'm doing this (roughly):
---
udp_sock = create_udo4_any_socket("");
evutil_make_socket_nonblocking(udp_sock);
udp_event = event_new(base, udp_sock, EV_READ|EV_WRITE|EV_PERSIST,
proc_udp_packet, (void*)base);
event_add(udp_event, NULL);
--
about kqueue
on OS X ;-)
Apologies for the noise
Matt
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
it/libevent-graphite
[1] http://graphite.readthedocs.org
[2] https://gist.github.com/bodgit/5387076
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
...
ptrdiff_t len = pos.pos;
You might find the reference manual helpful:
http://www.wangafu.net/~nickm/libevent-book/Ref7_evbuffer.html
yrs,
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
Hi
I'm porting some code from libevent 1.4 to 2.0 and in the 1.4 version some
of the code is using evbuffer_find find a pointer to the start of a
sequence then calculating a pointer difference from it:
u_char* end = evbuffer_find(input, pattern, 2);
...
ptrdiff_t len = end - input->buffe
r callbacks to event_callback too,
we can simplify their code significantly, and use common logic to make
all the callbacks in libevent get handled more efficiently.
best wishes,
--
Nick
*******
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ibevent/ . It implements the core
features, but needs more polish, documentation, and testing.
Thoughts?
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the bo
d immediately if
it's invoked from within libevent callback. That way we avoid
performance penalties *and* surprising results.
yrs,
--
Nick
*******
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
fer event in multithreaded code.
(See also the "Deadlock when calling bufferevent_free from an
other thread" thread on libevent-users starting on 6 August 2012
and running through this February. See also my earlier writeup
at http://archives.seul.org/libevent/users/Feb-201
ards,
Sebastian
Sjöberg***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
etc).
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
On Mar 29, 2013, at 6:32 PM, lesa Le wrote:
>
> I'm trying to write a program to retrieve data using evhttp_make_request().
> It needs to handle a significant amount of requests per second, to a decent
> amount of servers. Somewhere in the neighbourhood of 100s of servers, issuing
> several re
Hi,
I'm trying to write a program to retrieve data using evhttp_make_request().
It needs to handle a significant amount of requests per second, to a decent
amount of servers. Somewhere in the neighbourhood of 100s of servers,
issuing several requests per second.
What I'm currently working on is s
quot; -- have a look at the archives for more info on the
status of that one.)
(Wow, I should really answer that thread RSN.)
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
g this into the master branch.
There's nothing stopping us from tightening it up more in the future.
If anybody has more stuff that I should look at, please open a pull
request or something?
thanks,
--
Nick
***
To unsubscribe
es to use.
> ***
> To unsubscribe, send an e-mail to majord...@freehaven.net with
> unsubscribe libevent-usersin the body.
*******
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
You can see the test code at
http://pastebin.com/0136vEbe
-John
- Original Message -
From: Mark Ellzey
To: libevent-us...@freehaven.net
Cc:
Sent: Wednesday, March 27, 2013 11:20 AM
Subject: Re: [Libevent-users] Simple question about multithreading SSL
bufferevents.
On Tue, Mar 26
scribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
nnection_baes_bufferevent_new
would appear to be the ones to use.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
essier/Chandra.
Thanks,
-John
- Original Message -
From: Mark Ellzey
To: libevent-us...@freehaven.net
Cc:
Sent: Wednesday, March 27, 2013 7:23 AM
Subject: Re: [Libevent-users] Simple question about multithreading SSL
bufferevents.
On Tue, Mar 26, 2013 at 03:32:17PM -0700, John wrote:
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
talize a set of mutexes and set lock/unlock
callbacks via ssl. See
https://github.com/ellzey/libevhtp/blob/master/evhtp.c#L3160 as an
example.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
p_connection_new and
evhttp_connection_set_base, or should I keep using them for now?
BTW, I'm using 2.0.21.
Thanks
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ng for reads on
it and you're not trying to write on it. Is this implementable?
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ignoring "..., 35Got data from client
- ignoring it
) = 35
epoll_wait(3,
*******
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
initialization.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ct your events -- but you can still use event_init() and
> event_set() like you did before, just so long as you call event_init()
> first.
>
> --
> Nick
> ***
> To unsubscribe, send an e-mail to majord...@freeha
all event_init()
first.
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
o not close the FD i exhaust the files desc
> before
> > reaching the bug.
> >
> > --
> >
> -
> > () ascii ribbon campaign - against html e-mail
> > /\
>
>
>
> --
> Respectfully
> Azat Khuzhin
> Primary email a3at.m...@gmail.com
> ***
> To unsubscribe, send an e-mail to majord...@freehaven.net with
> unsubscribe libevent-usersin the body.
>
--
-
() ascii ribbon campaign - against html e-mail
/\
-
> () ascii ribbon campaign - against html e-mail
> /\
--
Respectfully
Azat Khuzhin
Primary email a3at.m...@gmail.com
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
using libevent2 (libevent-2.0.21-stable) i create this log:
[warn] event_del: event has no event_base set.
[err] event_assign called on an already added event 0x84de9e4 (events: 0x0,
fd: 0, flags: 0x0)
using this code:
void connection::listen_write_event() {
int rc = 0;
if (fd == -1) return;
t yet, but I'm sure a
customer will find a way to run into it when we least expect it.
Thanks again for the brain dump, and I'll keep you updated if I make any
further progress!
--Patrick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ble some kind of code that would be difficult or
annoying to write otherwise?
yrs,
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
probing
for, see here:
https://www.owlfolio.org/possibly-useful/notes-on-the-cross-platform-availability-of-header-files/
)
zw
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
* You can max out at 64 events. That's a nonstarter IMO.
**
The interface for libevent backends is straightforward but
underdocumented. I would be more than happy to answer any questions
you have. The shortest backend of general interest is poll.c; the
longest is epoll.c.
yrs,
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
**
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ST /proxy/ HTTP/1.1", upstream:
>> "http://127.0.0.1:8000/proxy/";, host: "localhost"
>> ..
>> nginx access.log:
>> :::127.0.0.1 - - [11/Mar/2013:19:38:15 +0400] "POST /proxy/ HTTP/1.1"
>> 200 13 "-" "-"
unsubscribe libevent-users
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
..
>>> 2013/03/11 19:38:22 [error] 24256#0: *120 sendfile() failed (32: Broken
>>> pipe) while sending request to upstream, client: :::127.0.0.1, server:
>>> localhost, request: "POST /proxy/ HTTP/1.1", upstream:
>>> "http://127.0.0.1:8000/prox
gt; "http://127.0.0.1:8000/proxy/";, host: "localhost"
>> ..
>> nginx access.log:
>> :::127.0.0.1 - - [11/Mar/2013:19:38:15 +0400] "POST /proxy/ HTTP/1.1"
>> 200 13 "-" "-"
>> :::127.0.0.1 - - [11/Ma
t;;, host: "localhost"
> ..
> nginx access.log:
> :::127.0.0.1 - - [11/Mar/2013:19:38:15 +0400] "POST /proxy/ HTTP/1.1" 200
> 13 "-" "-"
> :::127.0.0.1 - - [11/Mar/2013:19:38:22 +0400] "POST /proxy/ HTTP/1.1" 502
> 172 "-" "-"
> :::127.0.0.1 - - [11/Mar/2013
On 11-03-13 16:00, Alexey Ozeritsky wrote:
> libevent does something wrong:
>
> $ ./sample/https-client -url https://localhost/proxy -data 4K -ignore-cert
> Response line: 200 OK
> OK
>
> $ ./sample/https-client -url https://localhost/proxy -data 512K -ignore-cert
> Response line: 502 Bad Gateway
access.log:
:::127.0.0.1 - - [11/Mar/2013:19:38:15 +0400] "POST /proxy/ HTTP/1.1" 200
13 "-" "-"
:::127.0.0.1 - - [11/Mar/2013:19:38:22 +0400] "POST /proxy/ HTTP/1.1" 502
172 "-" "-"
:::127.0.0.1 - - [11/Mar/2013:19:39:16 +0400] "POST /proxy/ HTTP/1.1" 400 0
"-" "-"
>
> Oscar
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
sn't do any certificate validation
> so far as I can see, and as such gets zero protection from
> man-in-the-middle attacks. People who don't know how to use TLS will
> be copying our examples here, so we need to make sure to get t
chaos as they all randomly drain it).
>
What you want sounds kind of like something you could do with
evbuffer_add_reference. Or possibly you want the new function in
libevent 2.1-alpha, evbuffer_add_buffer_reference.
best wishes,
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
I'm trying to create a fairly low overhead repeater process which will
accept N connections (where N is going to be relatively small, in the
area of 5-12) connections from other processes and which will forward
incoming packets from one connection to all of the others.
conn1 --'hello'--> repeater
bev, dns_base, AF_UNSPEC,
"www.google.com", 443);
event_base_dispatch(base);
return 0;
}
*******
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
de?
--Patrick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
For some time now I have been working on libpropeller -
https://github.com/sergeyzavadski/libpropeller.
It is a high level multi threaded library, that has full HTTP support (but
is possible to build custom TCP servers as well). It is written in C++ and
using libevent's bufferevents as the founda
ull request for this branch:
>
> https://github.com/libevent/libevent/pull/47
Thanks!
Is there no way to do this *without* importing a big pile of code from
curl? That seems kinda extreme.
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
re hasn't been any further discussion of this on the mailing
list, I've decided to go ahead and submit a pull request for this branch:
https://github.com/libevent/libevent/pull/47
--Patrick
***
To unsubscribe, send an e
Hello,
Where do I free a persistent evhttp_connection after it has been closed?
In my code, I have a cache of evhttp_connections to possibly different
hosts. These connections are reused for multiple requests to the same
hosts. At some point, these hosts may send back a "Connection: close"
header
the event object, and is about to incref it when thread
1 deallocates it.
zw
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
teresting to see. Though, support using libidn isn't going to
happen in libevent itself since it's licensed under the GPL.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
l_hostname_validation.c | 168 +
sample/openssl_hostname_validation.h | 56 ++
7 files changed, 816 insertions(+), 1 deletions(-)
create mode 100644 sample/hostcheck.c
create mode 100644 sample/hostcheck.h
create mode 100644 sample/https-client.c
create mode 100644 sample/openssl
On Wed, Feb 27, 2013 at 11:13 PM, Patrick Pelletier
wrote:
> On 02/20/2013 07:26 PM, Jardel Weyrich wrote:
>
> There's X509_check_host for that, but I'm really not sure whether it's
>> enough or not.
>>
>
> Please correct me if I'm mistaken, but my impression is that
> X509_check_host only exists
ially being too feeble of an attempt to be
worth keeping.
--Patrick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ion
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
;
> event_enable_debug_mode() -- see
> http://www.wangafu.net/~nickm/libevent-book/Ref1_libsetup.html
>
> Also, try running with the latest 2.0.x-stable version maybe. Also,
> consider running under valgrind.
> *******
> To
Chromium used NSS?
[...]
> AFAIK, it has no callback support for this kind of "automatic error
> reporting", except for SSL_set_info_callback, which sets a callback to
> report errors and state changes for a given SSL connection. FWIW, Tor uses
> it (see src/common/tortls.c).
Yeah, I wrote that code. I wouldn't recommend SSL_set_info_callback,
though: it is a huge can of worms.
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
n maybe. Also,
consider running under valgrind.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
On Wed, Feb 20, 2013 at 9:03 PM, Nick Mathewson wrote:
> On Wed, Feb 20, 2013 at 12:42 PM, Catalin Patulea
> wrote:
> > On Tue, Feb 19, 2013 at 9:40 PM, Jardel Weyrich
> wrote:
> >> 2) Call SSL_CTX_load_verify_locations passing the path of the CA
> >> certificates installed by the aforementione
alls unless
> necessary?
I don't know of an API like that in openssl. (Anybody?)
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
rors after the fact (ERR_get_error, ERR_print_error, etc.) but I
would prefer not to clutter the sample with those calls unless
necessary?
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
debug_mode_on = 1;
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
On Tue, Feb 19, 2013 at 7:07 PM, Catalin Patulea wrote:
> On Tue, Feb 19, 2013 at 3:05 PM, Nick Mathewson
> wrote:
> >* It could sure use comments!
> Can you be more specific? This all feels like a lot of boilerplate to
> me. Parse the URL, initialize OpenSSL, create some bufferevents. I'm
>
whether I need to do this myself - any
idea?
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
> bufferevent_getfd(evcon->bufev)?
>
>> How does the attached patch look to you? Does it work as well/any better?
> I'll see about canarying it and will reply once it's been running for a while.
*******
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
nce it's been running for a while.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
On Tue, Feb 19, 2013 at 11:57 AM, Catalin Patulea wrote:
> On Tue, Feb 19, 2013 at 11:49 AM, Nick Mathewson wrote:
>> Could you be more specific about the good results, and how to
>> reproduce them? Or how to reproduce/observe the undesired behavior?
>> It would also be good to have an explanati
tdown(). In Libevent
2.0, though, you shouldn't have to worry too hard about these leaks:
they're library-global, not something that can grow unbound.
***
To unsubscribe, send an e-mail to majord...@freehaven.net wit
nybody
decides that reading le-proxy.c is a substitute for learning the
OpenSSL API and shoots themselves in the foot. :p
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
so we need to make sure to get the
security right.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
I am using 2.0.21-stable on windows. When shutting down the server I get 3
memory leaks (see below).
Is there a clean function I should be calling when using windows threads?
WARNING: Visual Leak Detector detected memory leaks!
-- Block 5344 at 0x01FE0040: 40 bytes --
Lea
y.c
sample_le_proxy_LDADD = libevent.la libevent_openssl.la -lssl -lcrypto
${OPENSSL_LIBADD}
sample_le_proxy_INCLUDES = $(OPENSSL_INCS)
+
+SAMPLES += sample/https-client
+sample_https_client_SOURCES = sample/https-client.c
+sample_https_client_LDADD = libevent.la libevent_openssl.la -lssl -lcrypto
${OPENSSL_LIBADD}
+sample_https_client_INCLUDES = $(OPENSSL_INCS)
endif
noinst_PROGRAMS += $(SAMPLES)
--
1.8.1.3
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
ions.
We saw a 7-fold reduction in crash rate with this patch.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
o unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
> *evcon)
> tmp = bufferevent_get_input(evcon->bufev);
> evbuffer_drain(tmp, evbuffer_get_length(tmp));
>
> + bufferevent_setfd(evcon->bufev, -1);
> evcon->state = EVCON_DISCONNECTED;
> }
>
> --
> 1.7.7.3
>
******
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
gt; strange happens to it before it crashes your program.
>
> Best of luck,
> --
> Nick
> ***
> To unsubscribe, send an e-mail to majord...@freehaven.net with
> unsubscribe libevent-usersin the body.
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
LLBACKS flags become
generally unneeded, and can be replaced by an "avoid reentrant
callback invocation" mechanism.
--
Nick
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
1 - 100 of 1958 matches
Mail list logo
