SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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 need to run a couple of daemons at startup as root, and I've inserted the commands into /etc/init.d/boot.local but they will not start up. Any ideas WHY this is happening?!
I've searched but have not found any answers to this problem.
Specifically, I want to run the following two commands:
I've got the same problem ! I worte a simple startup script to mount extra partitions upon bootup, stored in in /etc/init.d and created a shortcut to it in all run levels. It never gets executed and system logs say absolutely nothing about it. Even simple commands echo "something." doesn't work from the script and are not present in logs.
FUnny though, I copied the script tpconfig a config utility for Synaptics touchpad and created shortcut 'touchpad' under each rc#.d directory. Now, this works !!
I'm gonna dig deep into this to try and find out why my startup script is being skipped ?!
Check /var/log/boot.msg, maybe you'll find the problem mentioned there.
Did you try to start these commands manually? What happens?
Have you checked YaST runlevel editor? Maybe lircd is already started from there (or simply needs to be activated.
boot.msg shows that it loads boot.local and responds with a [DONE]. When I check the services, it's not started, and when i do a ps aux, I don't see it running. Entering the commands manually works just fine. For the lircmd, i have to restart x, so you can see it's a pain in the arse to start up the lirc daemon, then start up the lirc mouse daemon, then restart x...
I just checked the runlevel editor, and lircd/lircmd doesn't start until I manually start it.
Quote:
Originally Posted by kevkim55
I'm gonna dig deep into this to try and find out why my startup script is being skipped ?!
In my case, the script is not being skipped - the log shows that boot.local is being executed. The problem is that the daemons just don't get loaded, so I have no idea what the heck is going on between the running of boot.local and my login screen.
One more thing - Since I just want lircd to run under runlevel 3 and 5, and lircmd to run under runlevel 5, would it just be better to put a new script file with the lircd command in /etc/init.d/rc3.d and /etc/init.d/rc5.d, and a script with the lircmd command in /etc/init.d/rc5.d and somehow point to it from my sysconfig file?
Thanks for the help.
D
Last edited by dezireduser; 11-16-2006 at 08:30 AM.
Use yast - system - system services. Give it a chance to check all the available services. Some are identified fast but others stay as ???? until the scan is complete. If a service is available it will be on that list. Select the service and then the enable button. There may be some other pop ups to respond to before the job is done. I had trouble enabling lisa and gave up but have used this method for other services.
Use yast - system - system services. Give it a chance to check all the available services. Some are identified fast but others stay as ???? until the scan is complete. If a service is available it will be on that list. Select the service and then the enable button. There may be some other pop ups to respond to before the job is done. I had trouble enabling lisa and gave up but have used this method for other services.
Yes, that is what I have to do now (or run the lirc and lircmd commands as root), but I need to have it automatically start up on boot, and that's where the problem is... I'm gonna try Keruskerfuerst's suggestion in a bit, and see if that works (dunno why there should be a . before the commands, but other scripts have a ". /etc/init.d/blahh", so let's hope it works.)
Thanks for the help guys!
Last edited by dezireduser; 01-08-2006 at 09:24 PM.
I may be confused, happened before, but when I look at setting system services in yast, it looks like the changes are permanent. In expert mode, not moi, you even get to select if boot and which run levels. Most but not all services start in run levels 3 and 5. Some services like CUPS are also enabled in other parts of yast but all services are controlled here.
UPDATE: Ok, it all works now. I wrote a script for the lirc mouse daemon with a requirement that the lirc daemon must be running, and stuck it in the init.d directory.
Last edited by dezireduser; 11-16-2006 at 08:31 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.