[syslog-ng] SIGHUP kills syslog-ng on FreeBSD 3-STABLE

Balazs Scheidler bazsi@balabit.hu
Tue, 7 Dec 1999 22:51:42 +0100


On Tue, Dec 07, 1999 at 09:37:44PM +0100, Lowkrantz, Goran wrote:
> Hi,
> 
> Here it is.

This patch should solve the problem with SIGHUP, because it drops messages
while the configuration is initialized. The real problem is not solved
though, the error message says that for some reason syslog-ng cannot bind to
0.0.0.0:514. I'll check that out too later.

diff -u -r1.18 sources.c
--- sources.c   1999/11/22 18:26:16     1.18
+++ sources.c   1999/12/07 13:19:22
@@ -182,7 +182,10 @@
        CAST(log_source_group, self, c);
        struct ol_string *name = get_source_hostname(logmsg->saddr);

-       assert(self->super.next);
+       if (!self->super.next) {
+               log_info_free(logmsg);
+               return;
+       }
        logmsg->source = c;
        if (self->long_hostnames) {
                if (logmsg->flags & LF_LOCAL) {



-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
     url: http://www.balabit.hu/pgpkey.txt