I have setup an rsync server daemon on a Linux (Slack 12.1) box in order to keep a mirror of files for various workstations on the network. Those workstations are WinXP systems with Cygwin installed (rsync is 3.0.4 under Cygwin, as well as on the Linux server).

Usually things work fine, but I took a look at the log file on the server this morning and noticed that the time in the log is VERY incorrect.
For example, I initiated the backup (don't have it scripted- yet) on one workstation in a command-line window and watched it's output through to it's completion. The whole process took maybe 20mins at around 10:30pm.

In the log, I see the initial connection from the workstation to the server at the correct time (or thereabouts), but all the directory lists after 'receiving file list' have a log time of 5:30am!
The minutes and seconds are even in their expected sequential order- but the hour jumps ahead 7 hours.

Another workstation I had backing up last night also failed (I watched the file size grow in the repository on the server- around 600MB at the time- when I checked it this morning the size was down to 100MB!), so I checked to logs to see what happened and this is when I discovered the time problem.

Does this make sense to anyone? I'm very confused as to why this is happening as it makes debugging my rsync configuration a little difficult.

Thanks,

- skubik.

So, the computer clock is still correct? Not sure where you are in Canada, but a seven hour increase is suspiciously close to changing from local time zone to GMT. Not sure why this would be happening.

Ah! Yes, you're correct. I'm in Calgary, Alberta, and our timezone is GMT-7. So that takes the mystery out of the number of hours the time is different by. But not sure as to why it's converting the time to GMT. Perhaps there's something I neglected to set in Cygwin on the workstations, or perhaps on the Linux server for rsync?
Yes, on each workstation and the server, the time is correct- I even went into the Cygwin bash shell on the workstations to verify that it isn't using some obscure internal timer. They all check out- so I can only assume this has something to do specifically with rsync.
Any thoughts??