On Wed, Sep 30, 2009 at 11:19 AM, Paul Lesniewski <paul@xxxxxxxxxxxxxxxx> wrote: > On Wed, Sep 30, 2009 at 5:12 AM, Ralf Hildebrandt > <Ralf.Hildebrandt@xxxxxxxxxx> wrote: >> * Paul Lesniewski <paul@xxxxxxxxxxxxxxxx>: >> >>> And if you're feeling even more adventurous, might I ask you to revert >>> these changes and try the original patch again to be double sure it >>> kills the machine? It's just that this second version shouldn't be >>> that different than the first.... >> >> Done. Machine still working. I don't understand this :( > > Ralf, thanks a lot for being so willing to test this in your > production environment. Unfortunately, this makes things a little > more difficult to understand. :-) Hmmm. 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? -- 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
