Child Process Killed
TFigueiro at au.westfield.com
Thu Mar 24 03:39:24 CET 2011
> Do you think that might help?
You're looking for /proc/PID/oom_score; here, read this: http://lwn.net/Articles/317814/
Reducing memory usage will help, yes. And what Tollef said in his reply is the practical approach: add ram and/or swap. At some point the sum of the RESIDENT processes memory size is bigger than SWAP+RAM, and this is what triggers oom_kill.
The other way around is what you suggested yourself: reduce memory usage.
This electronic mail message, including any and/or all attachments, is for the sole use of the intended recipient(s), and may contain confidential and/or privileged information, pertaining to business conducted under the direction and supervision of the sending organization. All electronic mail messages, which may have been established as expressed views and/or opinions (stated either within the electronic mail message or any of its attachments), are left to the sole responsibility of that of the sender, and are not necessarily attributed to the sending organization. Unauthorized interception, review, use, disclosure or distribution of any such information contained within this electronic mail message and/or its attachment(s), is (are) strictly prohibited. If you are not the intended recipient, please contact the sender by replying to this electronic mail message, along with the destruction all copies of the original electronic mail message (along with any attachments).
More information about the varnish-misc