On Wed, Aug 12, 2009 at 05:23:17PM -0700, Jeroen van Aart wrote: > I am not sure if it's the kernel's OOM killer or postfix itself which > causes it to quit.
1. The OOM killer _always_ uses SIGKILL. A program is not even given the possibility to react. 2. root processes (like master) have a much lower propability of geting killed then the processes of other users. > Would postfix kill itself if it failed to allocate memory? That would be either a SIGSEGV if the kernel is unable to find any suitable memory or SIGABRT of the system library does it. > Or what is postfix' > behaviour under such high load conditions? It's being run with -o stress. "-o stress" or "-o stress=yes"? > Is it possible to find out if in fact the OOM killer killed it, lacking > a specific log entry indicating it? No. It does not at least match the behaviour of the OOM killer. If you want to know the culprit, patch master to output the informations of the siginfo_t structure, which includes things like sender (kernel/userland) and pid. Bastian -- She won' go Warp 7, Cap'n! The batteries are dead!
