user initscripts-ng-de...@lists.alioth.debian.org usertag 547394 + incorrect-dependencies thanks
The proposed patch is wrong. To ensure that netenv is executed before the network is brought up, it need to specify this in the header. And changing $local_fs to mountall-bootclean do not make sense either, as $local_fs is defined to be after mountall-bootclean. Here is my proposed patch, making sure the netenv script is started after the local file systems are available and before the network is brought up. diff -ur ../netenv-0.94.3/debian/init ../netenv-0.94.3-pere/debian/init --- ../netenv-0.94.3/debian/init 2009-09-22 10:27:54.000000000 +0200 +++ ../netenv-0.94.3-pere/debian/init 2009-09-22 10:28:22.716823000 +0200 @@ -7,8 +7,8 @@ # Provides: netenv # Required-Start: $local_fs # Required-Stop: $local_fs -# Should-Start: $network -# Should-Stop: $network +# X-Start-Before: $network +# X-Stop-After: $network # Default-Start: S # Default-Stop: # Short-Description: Start netenv at boot time Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
