Hello all. New to Linux. Anyway, I was wondering how to run an application after the OS is fully booted up. I cannot put it in boot.local as I need the network to be up. My backup app needs to communicate to another server so I need it to start after all the rc scripts are done.
abrahamr wrote:
> Hello all. New to Linux. Anyway, I was wondering how to run an
> application after the OS is fully booted up. I cannot put it in
> boot.local as I need the network to be up. My backup app needs to
> communicate to another server so I need it to start after all the rc
> scripts are done.
You can use boot.local even if you want it to happen at some later time. Create
a script file that boot.local runs. In that script, start with a ‘sleep xx’,
where xx is long enough for your network to be running, then execute the startup
script for your backup app. Don’t forget to make the script executable.
The second way is to put your script in /etc/init.d. The place a link to that
script in /etc/init.d/rc5.d. The link name should be named Sxx… These links
are executed in alphabetical order - you can have it executed whenever you want
it. If your machine only boots to level 3, then add the script to rc3.d.
Larry
On Sat, 19 Jul 2008 04:24:27 GMT
Larry Finger <Larry.Finger@lwfinger.net> wrote:
> abrahamr wrote:
> > Hello all. New to Linux. Anyway, I was wondering how to run an
> > application after the OS is fully booted up. I cannot put it in
> > boot.local as I need the network to be up. My backup app needs to
> > communicate to another server so I need it to start after all the rc
> > scripts are done.
>
> You can use boot.local even if you want it to happen at some later
> time. Create a script file that boot.local runs. In that script,
> start with a ‘sleep xx’, where xx is long enough for your network to
> be running, then execute the startup script for your backup app.
> Don’t forget to make the script executable.
>
> The second way is to put your script in /etc/init.d. The place a link
> to that script in /etc/init.d/rc5.d. The link name should be named
> Sxx… These links are executed in alphabetical order - you can have
> it executed whenever you want it. If your machine only boots to level
> 3, then add the script to rc3.d.
>
> Larry
Hi
You could also use the /etc/init.d/skeleton script as a basis to start
and stop, in here you can specify when the service starts eg after the
network is started, then running ckconfig (see man page) will add the
softlinks automatically for you.
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.23-default
up 7:47, 2 users, load average: 0.29, 0.31, 0.20
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
ln -s /usr/bin/appfoo /home/user/.kde/Autostart/shortcutname