The following archives are provided as a public service to the community. Opinions archived here do not necessarily represent the opinions of Open for Business or its contributors.
At 02:05 PM 12/8/04, Frank Bax wrote: >At 02:00 PM 12/8/04, Stephen J. McCracken wrote: > >>Frank Bax wrote: >>>At 01:37 PM 12/8/04, Warren Sanders wrote: >>> >>>>Frank Bax wrote: >>>> >>>>>I'm using this command: >>>>> rsync -atvz -e ssh [remote] [local] >>>>>to transfer a bunch of files form one system to another. Upon >>>>>inspection of received data, I notice about 50/50 of directories have >>>>>current or original timestamp. Why is that? >>Is the transfer being completed? I've seen that the timestamp is usually >>the current time on many copies until completed and then reset to the >>correct timestamp. > > >That could be it - transfer of 17G is only half done - some directories >appear to be complete, but timestamps are still current - will follow-up >in a few hours. Yes, I know installing disk to same system would have >saved a bunch of time, but that was not an option. Transfer complete - all timestamps appear to be ok now. Thanks.
| Home |