At 22.49 02/04/04 +1000, you wrote: >On the 28th March at 3am Daylight saving ended here, reverting back to 2am. > >Below is a list of my log directory. You will see that the logs have been >happily ending in "0000". >Then log entries up until 3am are in log files ending in "0000", then all >entries after 3am are in logs ending with "0100". >But here comes the good bit, the next day the logs end in "0000".
I noticed the very same behaviour when DST ended here in Italy last Oct; I was running 1.17 on win32. Here is my log directory for March 28 (start of DST). I was still running 1.17; switched to 1.18 on the same day but after 3 AM :-) 28/03/2004 23.17 pop3-200403272300 28/03/2004 2.14 pop3-200403280000 28/03/2004 23.44 smail-200403272300 28/03/2004 2.25 smail-200403280000 28/03/2004 23.51 smtp-200403272300 28/03/2004 2.53 smtp-200403280000 >Here is what I recon is happening. >The leap year is interfering with the daylight calculations. >When it is a leap year it is all ok, except on the day DST ends. Or starts ... >I am running Win2k SP4 & Xmail 1.17 Me, NT4 SP6a and (then) 1.17 Just a note: sometimes on Win32 whether a user is logged in affects timestamp recording. I have a filter.in VBS script which writes to a log file; when I'm logged in locally as Admin, timestamps are recorded as 24 local time; when I'm not logged in - or logged in from network - timestamps are recorded as 12 am/pm GMT. The script is always run by XMail (which runs under the System account). Ciao, Francesco - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
