Bug 92720

Summary:	syslog.cron script killall at end is too specific
Product:	Gentoo Linux	Reporter:	ivo welch <ivo.welch>
Component:	[OLD] Core system	Assignee:	Cron Team <cron-bugs+disabled>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description ivo welch 2005-05-15 11:29:19 UTC

This may be just my problem, but my /etc/cron.daily/syslog.cron file had "killall -HUP syslogd" at the end.  this creates a problem if one runs syslog-ng, because the process name is different.  as a result, there is no more log file after day 1.

when I originally installed the system, I played with what daemon I would be using, so this could be just my own fault.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Aaron Walker (RETIRED) gentoo-dev

2005-05-15 23:04:36 UTC

Firstly, I'm not sure why basesystem assigned this to us.  This has nothing to do with a cron daemon.

Secondly, syslog.cron is for sysklogd.  You cannot expect it to work with other syslog daemons.  If you think a cron script would be nice for the syslog daemon you are using, then submit a bug to the maintainer requesting one.