>>> 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?
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. > Like I said before, when I've found OOM taking place, it is time to > cycle the machine. It is much easier and quicker to cycle than to > correct the problem and restart all cancelled tasks. Have you found any > different? I hate to think that as OOM was cancelling things, that it > was producing a script that can be used to restart all cancelled tasks > (or something to that effect). The whole point of the OOM killer is to try to kill the "bad guy" while leaving the rest of the system up and running. If the bad guy was your main application (perhaps it has a big memory leak for example), then recycling the system may be the best thing to do. If your mission critical application is still up and running fine, you may want to consider restarting the killed processes. Or, you might want to leave them dead if they're just going to cause problems again. No general case can be made either way. Mark Post ---------------------------------------------------------------------- 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
