[Paul Slootman]
> Why the $remote_fs, instead of $network? Rsync should _not_ be used
> with network filesystems, as data is transferred excessively over
> the network in that case.

For the stop case, it is to make sure the script have something to
stop by making sure it is run before sendsigs.  For the start case, it
is just to document that it should run after /usr/ is mounted.
$remote_fs is not mounted networked file system in case such exist.
It is the point in time during boot when all file systems (like /usr/)
are garanteed to be mounted, as /usr/ can be a networked file system.

> Additionally, you may configure rsync to use a logfile instead of using
> syslog, which is why I put $syslog in the "Should-*" parts instead of
> the "Required-*" parts.

Should-* make sure it is started after that service if it exist.  As
$syslog is a fundamental package, it probably always exist, and thus
the two are equivalent.

> By the same token, if syslog should be available when rsync is
> running, doesn't it make sense to then stop rsync before stopping
> syslog?

Yes.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to