On Sat, Nov 13, 2010 at 06:01:09PM +0100, Heinz Diehl wrote: > On 13.11.2010, Arno Wagner wrote: > > > I don't know what criteria lead to activation of the OOM killer, > [....] > > How do you know it gets OOM-killed? I don't. By Occams Razor it is just my first suspected cause. Reason is that (if I understand correctly) all the memory has been allocated before the crash, so a NULL response from malloc is not the cause. But other than an unrelated program crash, that basically leaves the OOM killer. AFAIK shell (vm) limits block the allocation but do not SIGTERM/SIGKILL the process. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@xxxxxxxxxxx GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
