logcheck in dapper+hardy reports normal syslog restarts
Bug #116773 reported by
Caspar Clemens Mierau
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
logcheck (Debian) |
Fix Released
|
Unknown
|
|||
logcheck (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: logcheck
Logcheck from default install in Ubuntu Dapper through Jaunty reports cron driven restarts of syslog daemon like this:
System Events
=-=-=-=-=-=-=
May 25 06:25:07 medea exiting on signal 15
May 25 06:25:08 medea syslogd 1.4.1#17ubuntu7: restart.
Workaround:
edit /etc/logcheck/
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd [.0-9]+
Related branches
Changed in logcheck: | |
assignee: | ubuntu-server → nobody |
Changed in logcheck: | |
status: | New → Won't Fix |
Changed in logcheck: | |
status: | Won't Fix → Confirmed |
description: | updated |
Changed in logcheck (Debian): | |
status: | Unknown → New |
Changed in logcheck (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Thanks for your bug report. I'm not sure that this might not be of interest. If somebody managed to stop the syslog and start if some time later again it might well be a problem, but as I'm no member of the server team, there might a more relevant opinion on the matter.
Even if it gets accepted, I'm not sure we can get the patch easily into Dapper. Read http:// wiki.ubuntu. com/StableRelea seUpdates