Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
The one that fails on stop (anacron) may be "failing" because it wasn't started in the first place.
The one that fails on start (intel microcode) may be "failing" because it isn't relevant to your hardware (e.g. your running AMD or some Intel chip this wasn't designed for.)
Start/Stop scripts are based in /etc/init.d.
Just go there and look for the message you're seeing:
e.g.
grep "stopping anacron" *
That should give you the name of the file (probably anacron in that case). You can then look for the file start/stop in the run level directories (/etc/rc?.d where ? is the run level) by doing:
ls -l /etc/rc?.d/*file*
That should shown you files of the form:
S##file
K##file
Where the S is a start file and the K is a stop (kill) file, the ## is a sequence number and file is the same as that seen in init.d. These are typically links back to the file in init.d.
If you don't see an S##file for the anacron then you know it isn't being started so there is no need to stop it. You can simply remove the link for the K##file to prevent the stop attempt. (You may be able use chkconfig for this as well - see "man chkconfig".)
For the one that is failing on startup you can examine the file to see what it does. You can even try running it from command line to see if it gives any errors:
/etc/init.d/file start (or service file start).
You can then either try to fix whatever is causing it to fail OR you can remove the S##file so it doesn't try to start in the first place.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.