(Pete isn't here much) I remember this thread from a long time back. Messsage Sniffer doesn't take any particular efforts to lock the log file to prevent collisions. And he agreed that Microsoft Windows had the nasty habit of not always serializing writeln statements to a text file.
Scott wasn't inclined to add a spinlock feature so that the log lines could be cleaned up, on the bases that it was effort taken away from other priorities, that corruption tended to indicate a struggling server that ought to be upgraded, and general annoyance that calling an atomic function in the OS... didn't work. Andrew 8( -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darrell ([EMAIL PROTECTED]) Sent: Tuesday, March 01, 2005 2:39 PM To: [email protected] Subject: Re: [Declude.JunkMail] Log Corruption I though Pete had some locking mechanism built in to prevent overlapping. Pete....? Darrell Andy Schmidt writes: >>> Odd things is that I never get log corruption in message sniffer. So > somebody is writing out logs that don't get corrupt. << > > Maybe because he is running as a "service", thus can serialize the log > output? ------------------------------------------------------------------------ Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. --- [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.
