|
I'm using Debian 6. I manage to get it running on boot with the insserv command (with warning messages).
# insserv lsws
insserv: warning: current start runlevel(s) (2 3 5) of script `lsws' overwrites defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 5 6) of script `lsws' overwrites defaults (0 1 6).
----
The startup scripts were already in all the respective runlevel folders (eg. /etc/rc2.d, /etc/rc3.d, etc) prior to running the insserv command. I believe Litespeed has created them as it should be during installation.
But what is it preventing it from running?
I have re-simulated the entire process by reinstalling Litespeed and installing back again with the same configs. It still turns out that the insserv command has to be run before Litespeed can start up automatically on boot.
Could this be a bug? or is there a problem with the configurations on my system that prevents Litespeed from running automatically by default installation?
|