Jason Craig wrote:
Sloan wrote:
Jason Craig wrote:
Sorry, I've been struggling to find any information on this, mainly
because it is difficult to find proper search terms.
Say I've installed some software, like PostgreSQL, that adds a
beautiful script to /etc/init.d/ that starts or stops the server. Now
I want to start the server in, say runlevel 3, so I know I need to add
links to /etc/init.d/rc3.d/ but I'm having trouble finding information
on the proper way of doing this. Can anyone point me to some
documentation, or give a quick explanation of the numbers, letters
etc. used in these symlinks?
Unlike the old school unices where you tediously create symlinks by
hand, linux distros provide gui and cli tools to automate the process.
In yast, suse provides a runlevel editor under "system", or you can
simply issue a chkconfig or insserv command to set the runlevels for a
particular program.
See the man pages on those commands for more info.
Joe
Thanks, I forgot to mention that the main idea was that I couldn't use
YaST in this particular context.
S for start
K for kill
When entering a run-level, the S* scripts are executed.
When leaving a run-level, the K* scripts are executed.
K scripts are run in the reverse order of the S scripts.
The numeric parts of the name are used to control the
order of execution of the S* and K* scripts.
When adding some new software, if I have to add the links
by hand, then I just give them a higher S-number and
lower K-number than any of the other scripts in the
directory.
This method works on all systems which use the
Unix System V style init system.
BSD systems have a different mechanism for init,
and it's been too long since I last played with
one to make any comment on BSD init and /etc/rc.d
on those systems.
--Jason
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
