On Wed, Sep 30, 2009 at 12:15 PM, Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx> wrote: > * Paul Lesniewski <paul@xxxxxxxxxxxxxxxx>: > >> It may be possible that it's just one particular action or email >> message content that triggers a problem with this patch - in which >> case maybe SM gets caught in an endless loop eating all your server >> memory or the likes. You didn't happen to notice a runaway httpd >> thread when the load was skyrocketing, did you? > > Well, I INITIALLY applied the patch during daytime, at the time of > highest load. Maybe that was unwise and caused the runaway condition... So can I infer that the second version was never used during peak time? (and also that it has not been peak time yet since you reverted to the first version?) -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users