I'be got the same misbehavior with a custom init-script: # update-rc.d myinitscript defaults 99 update-rc.d: warning: /etc/init.d/myinitscript missing LSB information update-rc.d: see <http://wiki.debian.org/LSBInitScripts> Adding system startup for /etc/init.d/myinitscript ... /etc/rc0.d/K99myinitscript -> ../init.d/myinitscript /etc/rc1.d/K99myinitscript -> ../init.d/myinitscript /etc/rc6.d/K99myinitscript -> ../init.d/myinitscript /etc/rc2.d/S99myinitscript -> ../init.d/myinitscript /etc/rc3.d/S99myinitscript -> ../init.d/myinitscript /etc/rc4.d/S99myinitscript -> ../init.d/myinitscript /etc/rc5.d/S99myinitscript -> ../init.d/myinitscript
Whereas the myinitscript file contains: ### BEGIN INIT INFO # Provides: myinitscript # Required-Start: $network $remote_fs # Required-Stop: $network $remote_fs # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start the myinitscript daemon ### END INIT INFO I run: Linux version 2.6.28-15-generic (bui...@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #52-Ubuntu SMP Wed Sep 9 10:49:34 UTC 2009 -- [Jaunty] warning: missing LSB information https://bugs.launchpad.net/bugs/305587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs