RobCote

After searching for MONTHS on how the hell to have a freaking program run on startup i am fed up! i cannot find a simple solution ANYWHERE on ANY forum, everything is completely not user friendly. i see people crying every where that they are newbs and they get answers to their problems are are barely readable. I'm pulling my hair out trying to get a couple programs to just run on startup. i don't care how its done i just want it to do it and i want a SIMPLE COMPLETE DOORKNOB STEP BY STEP answer please please please. I am running:
Suse 9.1 pro

I want to run various scripts located in
/usr/local/bin/{their dir}
CS soure server script (its a shell script i use to start the server)
hlstats.pl (pearl script used for keeping track of stats on the server)
noip2 (dynamic dns updater software)
ventrilo (voip server)

ps. Pardon my madness i hope i haven't shot myself in the foot by complaining like i did, if i can get a solution i will be forever greatfull

**MOD EDIT: Topic changed to something less hostile with no yelling in it. - l_n

jeremy1701

Add the path to the apporpriate script at the end /etc/rc.d/init.d. Note that it may be different on Suse, I'm not sure of the exact location. The file you want to modify is init.d.
Jeremy

__________________
Registered Linux user #346571
"All The Dude ever wanted was his rug back" - The Dude

RobCote

I don't have this init.d file.

techieMoe

I believe init.d is in the /etc/ directory on SuSE.

__________________
Registered Linux user #270181
TechieMoe's Tech Rants

jeremy1701

Do you have /etc/init.d/boot.local?

Jeremy

__________________
Registered Linux user #346571
"All The Dude ever wanted was his rug back" - The Dude

big_k105

suse 8.2 has /etc/init.d/boot.local and that looks to be the place where you would add the commands you want to run at start up

__________________
BIG K aka Kyle
Programming Forums
www.kylekonline.com
Please don\'t PM me for help-- ask in the forums instead!

RobCote

Getting closer, i put them in boot.local, only one of them worked though,
it think its beacause its not a shell script, and is an actual program
what do i do if it is a shell script?
and a pearl script?

RobCote

some are still not running, no does boot.local run to early for some of these to work? because they would need to start whe nthe server has finished booting. they need to be the last things to run after a reboot

loft306

you can actualy put the commands that start tha app's in to any script tha runs at startup in gento we use /etc/conf.d/local.start look for a local start or the like in suse or maybe /etc/init.d/local and see if it tells u where to put them might also be /etc/rc??/start or local

__________________
~Mike ~~~ Forum Rules
Testing? What's that? If it compiles, it is good, if it boots up, it is perfect. ~ Linus Torvalds
http://loft306.org

RobCote

okay I got it to work using a work around with a rc.local file
i had to create a file that calls the scripts (rc.local) and i put it in /etc/init.d/
then you have to create a symlink in rcX.d that calls the rc.local script,
since my problem was it was executing before network drivers and such were ready, i had to name the link S99rclocal (S99 being the order of the scripts run on startup. i put this file in rc3.d so that its the last thing executed on a runlevel3 bootup.

I got my scripts to startup in seperate 'screens' that can be attached and detached using the screen -x XXX command,
Either way it was a nasty process but it works.