Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
Ok this maybe a stupid question but maybe the only stupid question is the one not asked!
I am trying to run Slimserver on a recently installed SUSE 9.3 box and the only way I can get it working is to run the Slimserver.pl manually but I would really like to be able to set it up so that the 'slimserver.pl --daemon' is started when the computer loads up as I will not always be there when the computer is restarted.
Ive looked into startup scripts something to do with init.d I think but the only Linux experience I have is through using computers in Uni.
thanks for the reply, however despite this the script is not running at startup, I can run the script manually to start the slimserver so I know the script is correct.
They differ (Slackware's BSD style vs. Suse's SysV style), that's true, but surely there is rc.local in suse also? It's location is another question...
it will be in one of the following directories:
/etc/
/etc/rc.d/
/etc/init.d/
/etc/rc.d/init.d/
Some of the above directories might be symlinks to some others, that's the way some distros are built. I don't really have any experience with suse, and in fact I've only taken a brief look at it's startup scripts on a friend's computer. Since it looked like a total mess to me, I can't be of any help with which one of the above is the correct one.
Through browsing many a forum with regards to Suse it seems that it does a number of things differently to other distros. The only reason I got suse was because there were some spare copies floating around uni, perhaps if I tried a more 'compliant' distro, maybe Mandrake? It would be easier for me to learn the ropes, as this is afterall, the whole point of the exercise.
Originally posted by Drfarfrompuken Thanks for all your help,
Through browsing many a forum with regards to Suse it seems that it does a number of things differently to other distros. The only reason I got suse was because there were some spare copies floating around uni, perhaps if I tried a more 'compliant' distro, maybe Mandrake? It would be easier for me to learn the ropes, as this is afterall, the whole point of the exercise.
The irony is that SuSE is to the Linux Standards Base standard. The more popular distros AREN'T to any defined standard. The whole Linux Standard things doesn't seem to be taking off very well although it's not real hard to see why. Personally, I think Slackware startup makes the most sense, but other than being unintuitive, the SuSE scripts are very well documented so it isn't too difficult to scan the filesystem to find the information that you need.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.