On 2008-08-01 at 19:49 Paul Slootman wrote:
On Fri 01 Aug 2008, becca23 wrote:
Yes it does appear that I have some sort of UTC disaster on my
hands. For
testing, both the Linux and Windows machine are virtual machines
on a VMware
server. The current UTC time for that one is 6:39. The Linux
> ... I am syncing between Windows and Linux and it was keeping the
> timestamps from the Windows side when copying to Linux. Even though
> both systems had the same system time, the timestamp was always one
> hour ahead of what it should be. ...
One hour, that sounds like Daylight Savings Time
On Fri 01 Aug 2008, becca23 wrote:
>
> Yes it does appear that I have some sort of UTC disaster on my hands. For
> testing, both the Linux and Windows machine are virtual machines on a VMware
> server. The current UTC time for that one is 6:39. The Linux UTC time is
> listed as 5:39 which agrees w
Yes it does appear that I have some sort of UTC disaster on my hands. For
testing, both the Linux and Windows machine are virtual machines on a VMware
server. The current UTC time for that one is 6:39. The Linux UTC time is
listed as 5:39 which agrees with worldtimeserver.com. The windows machine
On Thu, 2008-07-31 at 14:20 -0700, becca23 wrote:
> Yes, I assumed that was the problem, but I removed the -t option for a
> reason.
Well, to avoid resending the same files, you'll need the -t option
(unless you want to use -u and count on source file mtimes never being
touched to a time other tha
Yes, I assumed that was the problem, but I removed the -t option for a
reason. I am syncing between Windows and Linux and it was keeping the
timestamps from the Windows side when copying to Linux. Even though both
systems had the same system time, the timestamp was always one hour ahead of
what it
On Thu, 2008-07-31 at 11:24 -0700, becca23 wrote:
> I have been playing with rsync for several weeks now, and this is the first
> time I have encountered this problem. Rsync is including files that haven't
> been updated since the last sync. In fact, it's sending every file in the
> folder even if
I have been playing with rsync for several weeks now, and this is the first
time I have encountered this problem. Rsync is including files that haven't
been updated since the last sync. In fact, it's sending every file in the
folder even if it has not been updated. The current options I am using a
