System: i386 RedHat 5.1 (glibc6)
I have not seen this problem myself, but I am passing this on as I am the
linux support person here at USQ. This is what has been described to me,
and I haven't a clue as to why this is happening. However, I suspect that
it could be a glibc issue...
When linux boots up and uses the system time, it all looks ok. We are
GMT+10 hours here (Queensland Australia), and the bios clock is set at the
local time. /etc/localtime is a symlink pointing to the correct
/usr/share/zoneinfo/ file.
Write a file to a vfat-mounted dos partition with linux and the timestamps
look good - the correct (current) time as would be expected. (Of course,
same for timestamps on new files on the linux filesystem).
Boot into windows and the timestamps on any of these files are 10 hours
behind!
Create new files with the current timestamp with windose and all looks
good. But boot into linux and look at those files -- they are 10 hours
ahead! (Which means thay can be set for a time in the future).
This is obviously a problem related to the local time difference, but what
is going on?
Is windows at fault, or linux? Or have we just discovered the secrets of a
time-travel machine?? :-)
Thanks for any clues as to what could be going on and how to prevent this
from happening.
This querkiness is totally screwing up some scripts that are designed to
use file timestamps to keep in sync files that need to be kept on both
partitions.
Many thanks for any help.
Cheers .
Tony __________ Tony Nugent >> - Linux - << _--_|\
/ / / / __/ __ \ [EMAIL PROTECTED] >> UNIX power << / *\
/ /_/ /\ \/ /_/ / [EMAIL PROTECTED] >> on a pc! << \_.--._/
\____/___/\___\_\ UNIX Systems Officer, Faculty of Science v
University of Southern Queensland, Toowoomba Oueensland Australia
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-