Hi, i dug into this issue again a little and basically the patch looks strange without this:
--- src/dbus_service.c.orig 2008-03-16 12:03:00.000000000 +0100
+++ src/dbus_service.c 2008-03-16 12:03:08.000000000 +0100
@@ -1012,7 +1012,7 @@
}
static struct timeval *find_next_timeout (DBusConnectionState * cs, struct
timeval *tv) {
- next_timeout = 1;
+ next_timeout = -1;
twalk(cs->timeouts, find_timeout);
printf ("next timeout %f\n", next_timeout);
if (next_timeout == -1)
Basically the added code makes assumptions about next_timeout beeing -1
and then initializes it to 1 ?
I guess the original Author tried with -1 and failed (as i did) so
adding 80 lines of code for increasing the timeout from 200ms to 1sec is
bogus. The above eliminates the timeout completely when there is none
set (which is the case for me) but then dhcdbd does not wotk 100%
anymore. I get 2 green dots in the nm-applet but after some more seconds
it falls back to non connected. So my guess is that something either
needs polling in dhcdbd or some internal user does not set a correct
timeout.
Flo
--
Florian Lohoff [EMAIL PROTECTED] +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
signature.asc
Description: Digital signature
