> >>> On Sat, Feb 24, 2007 at 10:36 AM, in message
> <[EMAIL PROTECTED]>, Tom Duerbusch
> <[EMAIL PROTECTED]> wrote:
> -snip-
> > Is there a notification, that OOM has taken place? Two tangents on
> > this one...
> >
> > 1. Some signal (most likely to the console so our VM Console Manager
> > can take action), that can trigger a page?
> >
> > 2. Some inidication after the fact, that can be querried to know that
> > OOM happened?
You see it on the v-machine console, usually.
On Sat, 24 Feb 2007, 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.
Yeah ... I STRONGLY recommend this. Use SYSLOG. Feed it to VM.
It is just too easy to process SYSLOG traffic with CMS Pipelines
to not look into that option. In your /etc/syslog.conf, add a
line something like
*.info @vmhost
(TABs required between the "info" and the "@" sign.)
And then in some CMS v-machine, run a Pipeline like
pipe udp 514 | spec 17-* 1 | xlate a2e | console
Of course, you'll soon want to have something more interesting
than "console" as the consumer. This is a gross simplification.
(For example, I NEVER use the built-in "A2E".) But you get the idea.
-- R;
----------------------------------------------------------------------
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
