On Wed, 02 May 2007, Jared Hardy wrote:
...
> 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.
Peter is correct. Daylight savings time accounts for the difference
you're seeing (-0800 for PST, -0700 for PDT); we're currently in PDT.
> 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.
If you were on *nix, I'd say to strace the client when you were
executing the command which produces this error. Try wiping away that
client's WC and checking out a fresh one.
- application/pgp-signature attachment: stored
Received on Thu May 3 01:36:20 2007