** Changed in: logcheck (Ubuntu)
Status: Won't Fix => Confirmed
--
logcheck in dapper reports normal syslog restarts
https://bugs.launchpad.net/bugs/116773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
In /etc/logcheck/ignore.d.server/syslogd, there is already a regular
expression to match these sorts of things:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd [.0-9]{5}#[0-9]+: restart
\(remote reception\)\.$
However, as the original poster points out, this regular expression does
not actually work o
Why, though, would you want logcheck to report a routine operation?
Anything that is routine will become continually more mindless; it will
train me to ignore it. And, then I will naturally give a little less
thought to all logcheck emails.
I'm not proposing this log message not be displayed in t
** Changed in: logcheck (Ubuntu)
Status: New => Won't Fix
--
logcheck in dapper reports normal syslog restarts
https://bugs.launchpad.net/bugs/116773
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
This is not a bug, but a feature. And it is reported in other
distributions.
Debian:
Jun 20 06:33:12 master syslogd 1.4.1#17: restart.
RedHat:
Jun 17 04:03:14 localhost syslogd 1.4.1: restart.
I would suggest rejecting this bug since restart of syslog of very
valuable information, not a bug.
** Changed in: logcheck (Ubuntu)
Assignee: Ubuntu Server Team => (unassigned)
--
logcheck in dapper reports normal syslog restarts
https://bugs.launchpad.net/bugs/116773
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubun
Thank you for the quick reply. I see the point in your argument but can
add that this event is not reported in Debian or other distributions I
had so far. If it's a wanted feature I can live with that, than you'd
prolly add an example on how to prevent this event from being reported
to the document
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
