On Thursday 17 July 2003 07:04 pm, Matthew Melvin wrote: > On Thu, 17 Jul 2003 at 9:27am (-0400), Reuben D. Budiardja wrote: > > [...] > > > Now, I don't want to copy the whole thing in one sit since it's large. I > > want to do it incrementally during off-peak hours, so, say everyday > > between 2-3 AM I would copy 500 MB, and then the next day continue with > > another ~500MB, and the next day, etc, etc, until it's completed. The > > content of source directory will change, although not by much at all, so > > this needs to be able to keep trakc of that and sync with the changes. >
> root 30556 0.1 0.7 3200 2040 pts/5 S 08:48 0:00 ssh remote > rsync --server -logDtpr . /target/dir > > ... so after an hour has gone by, and it's 3am... > > kill 30556 > > ... which is cool since we've only killed that transport that leaves the > rync processes themslves to clean up any particuarlly transfered files. > On Thursday 17 July 2003 07:52 pm, Bret Hughes wrote: > How bout simply running rsync against the whole shebang but having > another cron job kill rysnc at the end of your time window? The next OK, those seems to be a more viable solution. Just kill the rsync after an hour, regardless how much data get transported. Will 'killall rsync' do it? Since of course I don't want to get up at 3 AM in the morning to kill rsync. If not, then a script needs to be written to get the pid and kill it, which I am not on how to do it just yet. Thanks for all who replied. but certainly if anyone else think of something cool would be greatly appreciated. RDB -- Reuben D. Budiardja -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
