Bug 104265 - syslog-ng SIGHUP
Summary: syslog-ng SIGHUP
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 1
Hardware: x86 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Marius Tomaschewski
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-11 20:44 UTC by Ioana Josephine Ciuca
Modified: 2005-08-12 10:58 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ioana Josephine Ciuca 2005-08-11 20:44:49 UTC 
Aleatory, syslog-ng-1.6.8-3 receives SIGHUP and restarts. This is definetly not
a normal behaviour. /var/log/messsages or /var/log/warn show no further
information, so I find it pretty hard to track down. Maybe you can give me any
hints in hunting this bug down?

Message in /var/log/messages:
syslog-ng[9173]: SIGHUP received, restarting syslog-ng
Comment 1 Dr. Werner Fink 2005-08-12 10:22:43 UTC 
IMHO this entry is INVALID because the manual page of syslog-ng shows:

       The  configuration  file is read at startup and is reread after receipt
       of a hangup (HUP) signal.  When reloading the configuration  file,  all
       destination  files  are  closed  and  reopened as appropriate. For more
       information about the configuration file, see syslog-ng.conf(5).
Comment 2 Ioana Josephine Ciuca 2005-08-12 10:53:25 UTC 
Ok, makes sense. I'm closing this as INVALID.
Comment 3 Marius Tomaschewski 2005-08-12 10:58:48 UTC 
Yes, the message "syslog-ng[9173]: SIGHUP received, restarting syslog-ng" is
not exact. Syslog-ng reloads as Werner wrote, but writes "restarting" instead
of "reloading".