"John N. Alegre" wrote:
> John and others who replied.
>
> Thanks for the comments.
>
> The problem actually had to do with a NT util called "Time Sync". I have a
> util called Tardis running on my single dedicated NT box. This util runs as a
> service and keeps the system time on that machine in sync with the atomic
> clock. Obviously an NT version of rdate, but it runs as a backgroud process and
> does so without fault. All my other systems, laptop included are dual boot
> NT/Linux systems. On the NT side of all these machines I run another NT util
> called "Time Sync". This keeps the system clock in sync with the clock on the
> dedicated NT box that is in sync with the atomic clock. When booted into
> Linux the Linux system clock just gets its time from the same source and all is
> well.
>
> Well somehow "Time Sync" appears to be broke on the Think Pad. Whenever it
> tries to resync with the LAN the date gets set back to sometime in 1999 and the
> time to something incorrect. Since I am on the Linux side 90% of the time I
> did not discover this problem till yesterday. Removing this util from the
> Laptop and using the rdate util suggested my Mr Aldrich takes care of the
> problem.
>
Any reason you are using timesync and not tardis client or k9 on the NT side? I
ran tardis clients on my windows boxes for a while with no problems.
Bret
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list