We have either not had SYSLOGD killed or still gotten console reports. In any case, our local Cat Herder instantiated a console watcher for OOM events. Works!
-- R; ----- Original Message ----- From: John Summerfield [EMAIL PROTECTED] Sent: 02/24/2007 06:10 PM To: [email protected] Subject: Re: Linux OOM Mark Post wrote:
The action gets written to the system log. It would be possible to have something looking through the log for those events. On a virtual memory exhausted system, that might be counter productive. If you transmit your syslog events to a separate logging system, that wouldn't be an issue.
A problem with monitoring stuff on another system is that, once syslogd kists killed, nobody's going to tell you what else. And if syslogd is first, the problem won't even be apparent. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
