Package: rsync Version: 2.6.9-1 Tags: patch User: [EMAIL PROTECTED] Usertags: incorrect-dependency
When testing dependency based boot sequencing, I discovered a minor bug in the init.d script for rsync. The start and stop dependencies are not optimal. The script should start after file systems and syslog is available, stop before file systems are umounted (and shortly before that, when all remaining processes killed by the sendsigs script). This patch solve the issue: --- rsync-2.6.9.orig/debian/init.d 2007-12-31 12:27:35.000000000 +0100 +++ rsync-2.6.9/debian/init.d 2007-12-31 12:33:07.000000000 +0100 @@ -2,10 +2,9 @@ ### BEGIN INIT INFO # Provides: rsyncd -# Required-Start: $network -# Required-Stop: $syslog -# Should-Start: $named $syslog -# Should-Stop: $syslog network +# Required-Start: $remote_fs $syslog +# Required-Stop: $remote_fs $syslog +# Should-Start: $named # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: fast remote file copy program daemon As the stop script do not seem to do anything except killing the daemon, that task might be better left to the sendsigs script in runlevel 0 and 6. If this is indeed the case, I recommend removing 0 and 6 from the Default-Stop list. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
