Re: [opensuse] adding links in /etc/init.d/rc*.d/

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: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: [opensuse] adding links in /etc/init.d/rc*.d/
    ... because it is difficult to find proper search terms. ... script to /etc/init.d/ that starts or stops the server. ... I'd put it somewhere late in the runlevel sequence of events. ... I'd also use YaST to start and stop the service. ...
    (SuSE)
  • Re: Best way to "Clone" a Linux Hard drive?
    ... >> near certainty, not a risk, since your server is busy enough to make you ... It's not logfile integrity, but file system integrity. ... let's take this into a runlevel where only three things run: ... What you should do is run a failover server as a mirror, ...
    (comp.os.linux.setup)
  • Re: [opensuse] Redesign of YaST Control Center
    ... This is your chance to share your ideas regarding YaST Control Center. ... server> "here are the options" ... in order to administrate remote boxes... ...
    (SuSE)
  • Re: KDE322 into 9.0
    ... > as an installation source in YaST. ... > directory on server: ... As long as I've been using Yast it's been loosing it ... Then I ran rpm -Uvf *.rpm against the lot ...
    (alt.os.linux.suse)
  • RE : Re: I got Linux server problem .. please help
    ... And another problem is that LPD service always have to be started manually after server starts and at the booting time it shows failed and bind '515 kinde of error is showwn at booting time. ... no more processes left in this runlevel. ...
    (RedHat)