without drift. I made my copy just take absolute
uptimes, but you could probably achieve most of the same thing by
implementing EV_PERIODIC for timers.
--
Scott Lamb http://www.slamb.org/
___
Libevent-users mailing list
Libevent-users@monkey.org
http
structures have changed
since the event_debug()s were written.
Best regards,
Scott
--
Scott Lamb http://www.slamb.org/
event-once-leak.patch
Description: Binary data
event-poll-leak.patch
Description: Binary data
event-signal.patch
Description: Binary data
.) It's
probably in my_own_biz_code().
2) You've saturated your network connection. How fast can you send
data, and how fast are you sending data? On Linux, sar -n DEV 1000
1 will show you bandwidth utilization every second (for 1000 seconds).
--
Scott Lamb http://www.slamb.org
On Nov 9, 2006, at 6:17 PM, Niels Provos wrote:
I submitted a fix along these lines to subversion. Please, check it
out and see if you can reproduce problems on amd64. I don't have
access to such a system.
Oh, by the way. I've been getting into buildbot lately. Are you
interested in having
On Nov 9, 2006, at 6:17 PM, Niels Provos wrote:
I submitted a fix along these lines to subversion. Please, check it
out and see if you can reproduce problems on amd64. I don't have
access to such a system.
Oh, buildbot also lets you force a build of a particular revision. So
you should be
hundredfold by time saved debugging the SWIG-generated
code later.
http://www.artima.com/weblogs/viewpost.jsp?thread=95863
--
Scott Lamb http://www.slamb.org/
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkey.org/mailman/listinfo
On Feb 22, 2007, at 6:32 PM, Niels Provos wrote:
Do you have an addition to the regression test that would allow me to
verify that the new code works as intended? If not, it would be most
appreciated :-)
There is one that verifies the quickly received signal case. Are you
talking about
Scott Lamb wrote:
libevent's monotonic clock detection is currently broken on all
platforms. The first attached patch fixes it. The second takes advantage
of it to remove the 5-second idle timeout where possible. This is
starting to become a big deal on Linux, where they've removed ticks from
Christopher Layne wrote:
On Thu, Jul 19, 2007 at 01:14:58PM -0700, Scott Lamb wrote:
When I use valgrind --tool=memcheck on a libevent-based program, it
gives the following complaint:
==15442== Conditional jump or move depends on uninitialised value(s)
==15442==at 0x4C0F2D3: event_add
Christopher Layne wrote:
On Sat, Aug 04, 2007 at 07:21:46PM -0700, Scott Lamb wrote:
Christopher Layne wrote:
On Thu, Jul 19, 2007 at 01:14:58PM -0700, Scott Lamb wrote:
When I use valgrind --tool=memcheck on a libevent-based program, it
gives the following complaint:
==15442== Conditional
Niels Provos wrote:
Thanks for the patches. I removed the default timeout. Your patch
had a bug where timeout_correct no longer set event_tv correctly. I
fixed that.
Oh, nice catch, thanks.
Unfortunatley, the regression test currently fails on Mac
OS X when compiled with -O2. Still
a5d264a55153e029e58eebb60840f0ed17a81071 Mon Sep 17 00:00:00 2001
From: Scott Lamb [EMAIL PROTECTED]
Date: Tue, 31 Jul 2007 14:41:38 -0700
Subject: [PATCH] remove rtsig, which is obsolete and broken
---
libevent/Makefile.am |2 +-
libevent/WIN32-Code/config.h |6 -
libevent/configure.in| 53 ---
libevent
intended to, and with a small patch it does.
--
Scott Lamb http://www.slamb.org/
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkey.org/mailman/listinfo/libevent-users
Marcelo Estanislau Geyer wrote:
Hi,
I'm development small program in C++ on Linux (Fedora 7 and Kdevelop).
When compiling the program, is appearing the following message:
undefined reference to `event_init'
I have add header event.h, but I am with difficulties to work with this
library due
Nick Mathewson wrote:
On Tue, Oct 02, 2007 at 09:35:48AM +0200, Robert Iakobashvili wrote:
[...]
libcurl has developed a good API for its integration with libevent.
libcurl project also maintains and develops a very good asynchronous DNS
client library, called c-ares (a clone of ares).
Trond Norbye wrote:
I thought that it was normal to name the libraries like
libname.so.major.minor.micro (eg: libevent.so.1.3.4) and create
symbolic links so the application may pick up the newest version of the
library (with the correct ABI) without re-linking the application.
As did I, and
Marc Lehmann wrote:
Hi!
On tuesday, I sent mail about various problems with libevent and its
current API as well as implementation. Unfortunately, the mail has not yet
shown up, but fortunately, it has been superseded by this one :)
In that mail, I announced that I will work on the
Marc Lehmann wrote:
That seems rather undesirable for many applications.
Well, its arguably better than libevents behaviour, which is simply
returning from event_loop, leaving the app unclear on what has happened
and what to do.
In any case, you can get the same behaviour as libevent by
Scott Lamb wrote:
* What's your use case for ev_loop_new() and ev_loop_default()'s bitmask
of allowed implementations?
libevents unconditional use of getenv raised concerns with me and
apperently some users on this list, too, so this is one way to disable
this (EVMETHOD_ANY instead
Christopher Layne wrote:
On Sun, Nov 04, 2007 at 04:23:01PM -0800, Scott Lamb wrote:
It wasn't what I expected; I was fully confident at first that the
thread-pool, work-queue model would be the way to go, since it's one
I've implemented in many applications in the past. But the numbers said
Marc Lehmann wrote:
On Sun, Nov 04, 2007 at 09:56:44PM -0800, Scott Lamb [EMAIL PROTECTED] wrote:
returning from event_loop, leaving the app unclear on what has happened
and what to do.
In any case, you can get the same behaviour as libevent by calling unloop
in case of an error, so
Christopher Layne wrote:
+ /* save previous handler setup */
+ if (sigaction(evsignal, NULL, sig-sa_old[evsignal]) == -1
+ || sigaction(evsignal, sa, NULL) == -1)
Not worth changing unless you're redoing the patch anyway, but is there
some reason you aren't doing
I'm trying to use the evdns client API for the first time (in tinc-1.1),
and I've noticed a few things:
1. There's no threadsafe API (see ticket 1827379). This is not necessary
for tinc but is good to have in general.
2. There's no way to cancel an outstanding resolve. (see ticket 1827307)
this
Ilya Martynov wrote:
Hi,
I wonder if anybody could elaborate what is the reason for setting
SO_LINGER option for sockets created by evhttp. I mean this part of code
inside of http.c:
static int
bind_socket_ai(struct addrinfo *ai)
{
...
linger.l_onoff = 1;
Marc Lehmann wrote:
On Fri, Dec 14, 2007 at 12:56:00PM -0800, Scott Lamb [EMAIL PROTECTED] wrote:
Tests and results here:
http://www.slamb.org/svn/repos/trunk/projects/socket_tests/index.html
The UNIX socket API has been standardized for a decade. But the standards
are vague on a lot
I was frustrated with the gap between bench.c and decent charts, so I
made the attached patch. It adds a simple Python program to generate
these with gnuplot. I've also attached sample output (one-active.png).
Best regards,
Scott
--
Scott Lamb http://www.slamb.org/
inline: one-active.pngAdd
be a
simpler way, but I don't see it.
Best regards,
Scott
--
Scott Lamb http://www.slamb.org/
evhttp: stream incoming responses, even if not chunked
From: Scott Lamb [EMAIL PROTECTED]
Signed-off-by: Scott Lamb [EMAIL PROTECTED]
---
libevent/http.c | 19 ++-
1 files changed, 14
Scott Lamb wrote:
(4) Detect while streaming that the client connection has been lost, so
that we know to stop sending chunks. Patch attached to return error code
in evhttp_send_reply_chunk(). (Wouldn't hurt to add error returns in
other places, but this is my immediate need.)
Hmm, my patch
Springande Ulv wrote:
Has anyone else seen this problem on Mac OS X? Otherwise I'll try to
debug more and come up with more specifics.
Also I also see that libevent seems to enter a while-true loop, grab all
CPU and freeze during handling of a write|timeout. I have a feeling this
is related
Derek Gottfrid wrote:
I noticed an oddity and want to check and see if anybody else was
seeing the same issue.
If I call a eventlib http server w/ GET and Keep Alive and then
follow it up with a POST on the same connection, then I see a 400 Bad
Request message returned. If I just call the
Alex Evans wrote:
hello. I'm fairly new to libevent and especially evhttp, so I have a query
whose solution may just be 'dont use evhttp that way'... the summary is: how
can I know if an evhttp_request object is 'freed' behind my back, and avoid
using it after it's dead?
I'm writing a simple
Jon Singler wrote:
Alex Evans wrote:
hello. I'm fairly new to libevent and especially evhttp, so I have a query
whose solution may just be 'dont use evhttp that way'... the summary is: how
can I know if an evhttp_request object is 'freed' behind my back, and avoid
using it after it's dead?
I'm
mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
--
Scott Lamb http://www.slamb.org/
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
33 matches
Mail list logo
