Bug 104265

Summary:	syslog-ng SIGHUP
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Ioana Josephine Ciuca <Josephine_k>
Component:	Basesystem	Assignee:	Marius Tomaschewski <mt>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 1
Target Milestone:	---
Hardware:	x86
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

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".