Mailinglist Archive: opensuse (3637 mails)

["Geordon VanTassle" <gvantass@xxxxxxxxxxxxxxxx>]

Ok, given that I have just now learned about insserv and the way that SuSE
sets the runlevel for stuff.

Now if I install stuff manually (from source, for example) that installs an
initscript (the latest NetSaint in this instance) and I add the appropriate
header information and run insserv, will that set the symlinks right?

If  my logic is correct, that should work.  Am I right?

THanks,
Geordon
----- Original Message -----
From: "Philipp Thomas" <pthomas@xxxxxxx>
To: "Tara L Andrews" <tla@xxxxxxx>
Cc: <suse-linux-e@xxxxxxxx>
Sent: Tuesday, May 08, 2001 7:53 PM
Subject: Re: [SLE] Notes and comments on SuSE 7.1 install


>to install generic RPMs without having to move around rcN symlinks.

Well, beware of one caveat. If you examine one of the scripts in
/etc/init.d, you'll see that they now have LSB conforming headers which
allows /sbin/insserv to automatically create and delete appropriate
symlinks in the runlevel directories (see 'man insserv' for more
details).

No generic RPM I've encountered so far has init scripts that conform to
this but instead install the script and the symlinks. The next time
insserv is called (all our packages that add init scripts do so in the
post install script), those symlinks will get zero as priority (e.g.
S0xxxxx) and thus will be started or stopped at the wrong time.

As distributions get closer to the LSB spec (including ours), points
like this will (hopefully) vanish.