Package: nbd-server Version: 1:2.9.15-2 Tags: patch User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-dependency
I just did a test installation of Debian/Squeeze, and noticed the nbd-server init.d script is started before rsyslog. I tested to move it after the rsyslog service is operational, and running 'init.d/nbd-server start' during boot did not cause the kernel to generate some syslog messages, nor did it generate any syslog messages itself. Can it generate syslog messages when something fail, or perhaps cause the system to crash and hang? If so, it might be a good idea to start it after the syslog collector is active, to make it easier to figure out such problem using the syslog messages. This patch will implement this. --- nbd-2.9.15/debian/nbd-server.init.d 2010-05-01 23:09:37.000000000 +0200 +++ nbd-2.9.15-pere/debian/nbd-server.init.d 2010-05-01 23:10:11.000000000 +0200 @@ -14,8 +14,8 @@ # ### BEGIN INIT INFO # Provides: nbd-server -# Required-Start: $remote_fs -# Required-Stop: $remote_fs +# Required-Start: $remote_fs $syslog +# Required-Stop: $remote_fs $syslog # Should-Start: $network # Should-Stop: $network # Default-Start: 2 3 4 5 In any case, it should not harm to start a bit later during boot, so the patch should be safe to implement. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
