Here is one more thing to consider...
If the time required for a complete sync is longer than the daily time slot,
you also want to make sure
that every change will eventually be sync'ed. That is, if every day you
change the same 1000 files and
rsync is capable of syncing only 800 of them per day, then possibly, some
files that are at the end of the list
may never be sync'ed. This depends of course how rsync is implemented.
If this is a real problem, you may consider breaking the sync space into
smaller sub directories and performing
piecewise syncs with some kind of round robin (yuck).
Tal
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Tim Potter
> Sent: Wednesday, April 04, 2001 3:11 PM
> To: Alberto Accomazzi
> Cc: Sean Berry; 'Dirk Markwardt'; '[EMAIL PROTECTED]'
> Subject: Re: Need for an --operating-window feature ???
>
>
> Alberto Accomazzi writes:
>
> > FYI, rsync has a good cleanup mechanism that kicks in when you send it
> > a SIGHUP. It removes/renames temporary files as appropriate, sends a
> > signal to its child process, and exits. I use this all the time to
> > gracefully stop transfers (see the pseudo-code in my previous message).
>
> I've been doing some mucking around with maximum connect time and
> the like. Rsync returns error code 20 when it has been
> terminated by a SIGUSR1 or SIGHUP. I use this to work out
> whether the connect time limit has been reached or whether rsync
> completed within that time.
>
>
> Tim.
>
>
