[syslog-ng] [Bug 199] syslog-ng 3.3.6.90 sometimes exits on SIGHUP on Solaris 10 SPARC

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=199


Gergely Nagy <algernon at balabit.hu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |algernon at balabit.hu
         AssignedTo|bazsi at balabit.hu            |algernon at balabit.hu




--- Comment #1 from Gergely Nagy <algernon at balabit.hu>  2012-09-26 17:50:31 ---
This is interesting. The exit happens due to syslog-ng signalling itself with SIGQUIT, because it ends up in a branch where the new configuration could not be
loaded, and reverting to the old one failed aswell.

I'll try to reproduce it myself, but in the meantime, could you perhaps change line 518 of lib/mainloop.c to send a SIGABRT instead of a SIGQUIT? If you enable
core dumps afterwards, then syslog-ng should dump a nice core, which might help us figure out what went wrong.

Also, are there any error messages coming from syslog-ng in the logs by any chance?


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.