92720 – syslog.cron script killall at end is too specific

Bug 92720 - syslog.cron script killall at end is too specific

Summary: syslog.cron script killall at end is too specific

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Cron Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-05-15 11:29 UTC by ivo welch
Modified:	2005-05-15 23:04 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

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