init script link clashes, debian, update-rc.d, /etc/rc2.d
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As you can see, several script links all have the number 19 ...
Is it normal for Debian to give init script links identical numbers or should I try to change this?
If so is this a case of just changing them by hand or should I be using some kind of automated tool like 'update-rc.d'?
[...]
hi,
This is normal, I have plenty of 20s for example.
Certainly, you can edit those numbers. Moreover you can do it, whichever way you like.
Question is: what for?
I don't think changing order of those scripts will help, unless you proved that already by running them manually. I suspect some configuration or network problems, rather than just wrong order.
What kind of error do you get running them?
-- KTG
Last edited by ktgajowniczek; 12-05-2007 at 08:51 AM.
I was not getting any actual error messages per se. However, NIS (ypbind) absolutely needs to be started before autofs it seems and in the initial configuration this was not happening. When I manually changed the link making autofs a greater number than (hence starting after) nis it worked fine.
I am not certain this is a Debian problem as I was simultaneously setting this up of Fedora which had a similar problem of the domainname variable not being set properly. It seems that whilst NIS and and autofs and easy to install, they need some tweaking to interact correctly post installation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.