> Jared Hardy wrote:
> > Last Changed Date: 2007-05-02 10:48:05 -0700 (Wed, 02 May 2007)
> > One strange thing is the "-0700" -- we are PDT, so shouldn't it be
> > "-0800"? Otherwise, the time looks correct.
On 5/2/07, John Peacock <email@example.com> wrote:
> That would suggest to me that someone messed with the timezone on the PC
> (possibly because the DST patch wasn't applied). I'd download this:
> and test if the DST patch was applied or not (it won't apply it twice).
After my last e-mail I downloaded the official DST patch from M$:
Every time I try to install it, on every affected client, it said a
newer patch had already been applied. Besides, as Peter Samuelson
noted, we are past daylight savings time now, with or without the
Peter Samuelson wrote:
> I assume by PDT you mean North America Pacific Daylight Time, which is
> -0700. North America Pacific Standard Time is -0800.
Every installer I've ever used says U.S. Pacific time is GMT-08:00, so
I guess I'm confused on that point. The windows clients all say
"Current time zone:" is "Pacific Daylight Time", and "date" on the
server outputs "Wed May 2 16:10:31 PDT 2007", where I assume
PDT=Pacific Daylight Time.
Either way, the time reported by the clients and both servers
(current and former) are in sync down to the second, as far as I can
easily tell, so I still doubt "bogus date" is the real issue. I
strongly suspect the error message is merely an artifact of some other
WC format issue. I also find it suspect that these error messages come
up with commit, or an immediate cleanup after the affected commit, but
at no other time. It definitely doesn't affect the server state, nor
any other client. The "bogus date" is only ever reported on the client
the commit was run on. Even then, the update/resolve cycle removes any
evidence of any "bogus date" ever occurring.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu May 3 01:21:46 2007