rsync - Oct 2002 - HELP !!! Problem with file timestamps updating "weird" during rsync data pull

Running rsync 2.3.1, 2.4.1, and 2.5.5 on Solaris 8 on various system.

I'm using rsync to pull data over for collecting performance data for 
graphing in Orca.  What I'm seeing is the timestamps from time to time of 
the data files is being setup "weird" on the system the data is being 
pulled to.

The timestamp should match that of the system the data is pulled from right 
?  Well, it doesn't from time to time.  The time stamp sometimes gets 
updated as just "Oct 16 2002"

I'm having problems with Orca dying for no good reason or it remaining 
running but it just stops graphing.

This timestamp thing is the closest thing I can find to a problem right now.

I'm calling rsync like this:

   
SRC_DIR=${LOGIN}@${SRC}:/local/home/perfboy/orca/var/orca/orcallator/${HOSTNAME}/
    DST_DIR=/local/home/perfboy/orca/var/orca/orcallator/${HOSTNAME}

    rsync -a -q --delete -essh ${SRC_DIR} ${DST_DIR}

Any idea why rsync might be doing this ?

--
........................................................
......... ..- -. .. -..- .-. ..- .-.. . ... ............
.-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...

Sean O'Neill

On Wed, Oct 16, 2002 at 01:36:10PM -0500, Sean O'Neill
wrote:
> The timestamp should match that of the system the data is pulled from right
> ?  Well, it doesn't from time to time.  The time stamp sometimes gets 
> updated as just "Oct 16 2002"
This is what most unix systems display for a future date.  I'm guessing
that the clocks on your systems are not in sync -- that the clock on the
receiving end is behind the sending end, which causes files that have
been recently modified on the sender to show up as having future dates
on the receiving system.

..wayne..

At 12:10 PM 10/16/2002 -0700, Wayne Davison wrote:
>On Wed, Oct 16, 2002 at 01:36:10PM -0500, Sean O'Neill wrote:
> > The timestamp should match that of the system the data is pulled from 
> right
> > ?  Well, it doesn't from time to time.  The time stamp sometimes
gets
> > updated as just "Oct 16 2002"
>
>This is what most unix systems display for a future date.  I'm guessing
>that the clocks on your systems are not in sync -- that the clock on the
>receiving end is behind the sending end, which causes files that have
>been recently modified on the sender to show up as having future dates
>on the receiving system.
Ahh, excellent point.  These systems aren't as tightly controlled as our 
development systems.  I'm not sure if NTP is setup or setup and running 
correctly.

Thanks, I'll check this out.


--
........................................................
......... ..- -. .. -..- .-. ..- .-.. . ... ............
.-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...

Sean O'Neill