I have an odd issue that I can't seem to figure out.
We have Windows XP boxes that connect directly to RH Linux boxes and the Linux box acts as a router / gateway. We have this setup repeated about 25 times in our environment and it works as we need. (25 Windows boxes connected to 25 Linux boxes - for clarity)
The only problem is related to the latest DST change. The Windows XP box has 2 shared directories that the Linux box dumps data into. The Linux box completes a test run and dumps the data into an smb share which resides on the windows box. The only issue is that the timestamp is always 1 hour in the future. I have verified that the clocks are correct on both boxes, and even synced up the HWclock to make sure. If I touch a file on the smb share and then stat it, this is the result:
Access: 2009-11-04 11:47:28.000000000 -0500
Modify: 2009-11-04 11:47:28.000000000 -0500
Change: 2009-11-04 10:49:30.000000000 -0500
The "Change" time is correct, but the other 2 are not. I can't reboot some of these boxes for quite some time, but it causing some major problems. Is there an explanation or solution to this problem?
My problem is very similar to this one
These timestamps are only wrong if I create a new file on the smb share, but not locally. I also created a new share and when I touch a file in the new share, it has all the correct times. It's driving me nuts, and I am hoping someone has some clues or something I can try.