Hello,
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.
There is another reason you should use insserv; with openSuSE 10.3 it
could happen that a symlink to rc3.d (or which runlevel you want) simply
is not enough to get the scrip executed at system start.
If parallel startup of independend services is enabled (that is, in
/etc/sysconfig/boot "RUN_PARALLEL" is set to "yes") your service needs
an entry in .depend.start. insserv or chkconfig writes the corect
entries (using the "Required-start" tags from the skript).
(Please correct me if I'm wrong, but we had some service that simply
would not start even though we had it linkdes to rc3.d until we made an
entry in .depend.start. Well, it would allso work to set "RUN_PARALLEL"
to "no", but this would increase the startup time.)
Thanks, I forgot to mention that the main idea was that I couldn't use
YaST in this particular context.
How odd - I'd love to know what context that might be (boggle).
Well, as for YaST I think there are some reasons why someone wants to
avoid it; if I want to change something quick, I usually don't start
YaST as I am to impatient to wait for it to complete. (insserv mostly
does the job and is much quicker.) Another reason could be another
Distro - this stuff isn't exactly SuSE-specific. The last possibility
comming to my mind would be acces from a text-terminal with extremly
spartanic encoding, so YaST would simply be unusable. (As strange as
this might sound, we have a customer with such a terminal to access his
servers. Most of his boxes are AIX, but some are SuSE Linux, and if we
don't want to run several corridors to the server-room we simply use
this terminal.)
So, I think the possibility of a SuSE-Box with seldom used YaST is not
as far-fetched as it seems to be.
Till then,
Ortwin
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
