-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Wednesday 2007-05-02 at 13:27 +0100, G T Smith wrote:
The (or one of the) right way to do it is to use 'insserv'
insserv squid
and all dependency is resolved and things will get started in right order. Yes you can do it in YaST but that will take much longer time than to type in this commando.
chkconfig is more complete - it calls insserv, in fact.
I think YaST does something slightly different to insserv, my /etc/insserv.conf file contains no references to squid (or a lot of other stuff which is enabled via YaST) there is a named entry in this file but again this was originally enabled via YaST.
Doesn't matter.
I think this may be a case of use insserv or use YaST but not both, as YaST may not update the /etc/insserv.conf file.... I am not going to test this but this could lead to duplicate entries in the runlevel folders....
Don't worry about that file, and use yast, insserv, or chkconfig indistinctly - the master "configuration" isn't there.
Thanks, that clarifies something for me, while it was fairly obvious that insserv would not work if the relevant script was not in /etc/init.d, what was not clear to me was how accurate the man page was for the SuSE configuration (e.g. /etc/insserv.conf.d/ does not exist)... and what the interactions were with other tools. I would guess that what YaST does is provide a GUI front end for chkconfig. Been a bit lazy about finding out what the command line options were given that the GUI did the job .... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGOKltasN0sSnLmgIRAsdlAJ9J/ugzqMlnkhIWp4UZeNZgAHQ0/ACdG+JN 7sO8Jc1Pf4pG9IZwsOS4wr8= =AM25 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org