On Wed, Sep 15, 2004 at 09:58:41AM +0200, Ralf Hildebrandt wrote: > > Because current clamd implementation is not to "die" on > > memory allocation error, but sleep. > > It doesn't die, it's being killed by the kernel.
No - clamd does a malloc and that fails. Then instead of dying (which would be the proper thing to do IMHO), it sleeps a few microsecs and then tries to malloc the memory again. Infinite loop occurs... I don't understand why it does that. I mean, if it failed to get memory once, why expect it to get better? At least have it try only 3 times or something - and then exit. [people running softlimits would almost invariably also be calling clamd under a supervise script, so if clamd died, it would be auto-restarted. That's the condition we are trying to achieve] -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 ------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
