I'm not really concerned about the former. Will you care to elaborate on the latter? I would think that the -c option (maxsmtpd) on tcpserver would mitigate that.
-- -Eric 'shubes' On 06/09/2011 09:02 AM, Dossy Shiobara wrote: > Don't forget that softlimit not only prevents misbehaving software from > running away and degrading the system's performance, but it ALSO > prevents resource starvation denial of service attacks. > > > On 6/9/11 11:45 AM, Sam Clippinger wrote: >> Remember that the "softlimit" program only limits the maximum amount of >> memory a process can use; it doesn't dictate how much it*will* use. It >> was written as a last resort for stopping processes that were out of >> control and leaking memory. It's big flaw is that you never get a >> simple "out of memory" error -- all you see are inexplicable bugs like >> the one Ron has been battling because (in this case) OpenSSL can't >> allocate a buffer or whatever. Given the number of problems it seems to >> create, I'd vote for simply removing it. > > -- > Dossy Shiobara | "He realized the fastest way to change > [email protected] | is to laugh at your own folly -- then you > http://panoptic.com/ | can let go and quickly move on." (p. 70) > * WordPress * jQuery * MySQL * Security * Business Continuity * > > > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
