Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I am running Slackware 9.1. I have some scripts in /etc/rc.d, namely rc.sendmail, rc.httpd and rc.samba, that refuse to start at boot. They are executable. They work when run from the command line as root, ie: /etc/rc.d/rc.sendmail start. They are specified in rc.M. Other files in rc.M, like rc.mimedefang, rc.bind, etc., start at boot just fine. I've also put the the troublesome scripts in rc.local, like:
in rc.local and that doesn't work either. They ALL work from the command line. Right now I have a cron job that kills and starts them every so often to make sure they are up. That works, but I want to know how to fix the startup scripts. Any help?
slackware looks different, but in other *nixs*, there are typically directories of the form
rcN.d, where N is run levels 0-6, e.g.:
cd /etc/rc.d
ls -CF */*sendm*
init.d/sendmail* rc1.d/K30sendmail@ rc3.d/S80sendmail@ rc5.d/S80sendmail@
rc0.d/K30sendmail@ rc2.d/S80sendmail@ rc4.d/S80sendmail@ rc6.d/K30sendmail@
The rcN.d contain symlinks to init.d/sendmai which are executed when entering that runlevel.
Yes, Slackware is quite different. No init.d directory. As a sidenote, after initial installation all 3 services started fine from /etc/rc.d/rc.M script. I'm not sure what happened along the way. I did install MIMEDefang and it runs just fine from rc.M, but somewhere along the line the others quit. And it looks like rc.local doesn't do anything anymore. I tried running any command in there and it never executes on boot...
One thing I've noticed, in particular after installing mysql and apache myself from source some services fall to start when run from rc.M as well as rc.local being ignored, solution I found was to remove the "." dot at the start of the command to start the daemon in rc.M i.e if it's
. /etc/rc.d/rc.mysql start
removed the dot to make it
/etc/rc.d/rc.mysql start
don't know if it's a timing issue or the daemon is blocking the rest of the script from being run but doing that solved it for me. Trial and error and the use of echo "Now starting whatever daemon" can help you pinpoint which particular one is acting up.
I think you may be on to something there. I haven't tried your suggestion yet, but I just got done doing some brainstorming and testing. The problem started after I added MIMEDefang to rc.M. I removed it and things starting runnin as normal, all init scripts running at boot. I added MIMEDefang to rc.sendmail and everything seems to run better now.
It could very well have been the "." , though this way is probably better for me since it starts and stops all mail related services in one command.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.