Christoph Biedl wrote...
> Starting system logging: syslog-ngConnection failed; error='Network is
> unreachable (101)', reconnect='10'
> start failed.
Reading the sources: This message is generated at afsocket.c:765 within
afsocket_dd_reconnect, a function that is not used much. I /think/ it
is safe not to return an error condition if the connect fails but I am
not sure about possible side effects I might have overseen. See the
attached patch for a simple but not very civilized workaround. Status is
"works for me".
But _please_ bring this matter to the upstream. The bug is still present
in the recently released syslog-ng 2.0.0.
Christoph
--- afsocket.c.ORIG 2006-08-08 21:22:48.000000000 +0200
+++ afsocket.c 2006-11-05 17:23:38.000000000 +0100
@@ -762,7 +762,7 @@
close(sock);
self->reconnect_timer = g_timeout_add(self->time_reopen * 1000,
afsocket_dd_reconnect_timer, self);
- return FALSE;
+ /* Connection failed but reopen will take care of that */
}
return TRUE;
