Correct. What I was saying I disagreed with was the concept that it only occurred on struggling servers. This test machine was very lightly loaded and we saw log corruption.
Darin. ----- Original Message ----- From: "Pete McNeil" <[EMAIL PROTECTED]> To: "Darin Cox" <[email protected]> Sent: Tuesday, March 01, 2005 7:30 PM Subject: Re[2]: [Declude.JunkMail] Log Corruption On Tuesday, March 1, 2005, 7:14:31 PM, Darin wrote: DC> I disagree with the struggling server logic. We saw the log corruption in a DC> test environment a year ago that had minimal traffic, say a couple thousand DC> messages a day. It was a dual 1.4GHz processor with 1 GB RAM and 10k RPM DC> SCSI drives. Load was only about 1-5% during testing. Heavier loads will cause more processes to "collide" and so log corruption is likely to be more pronounced in those situations. _M --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
