[SSI-users] Re: [SSI-devel] [RFC] service command equivalent on suse

[Brian J. W. <Bri...@hp...>]

En Chiang Lee wrote:
> Hi all,
> 
> SuSE does not seem to have an equivalent of the Fedora/RedHat service 
> command which is used to start rc services. On SuSE, the /etc/init.d/* 
> scripts are called directly to start and stop services. However, some 
> services have soft links /sbin/rc<servicename> (google searches give 
> this for the service equivalent) which allow the users to use
>     /sbin/rc<servicename> start
> where, on RH/FC, they would have used
>     service <servicename> start
> 
> OpenSSI has a modified version of the service command which uses the 
> onclass/onsvc commands to start and stop services in the cluster. To 
> provide this on SuSE, as part of the install of aaa_base, we could:
> 
> 1. replace the /sbin/rc* links with small scripts which call 
> /etc/init.d/* through onclass i.e. code the service command into these 
> scripts.

This sounds tedious, unless we wrote something to automatically generate 
a small script for every available service. We would also need some 
strategy to make sure every new service installed after OpenSSI had this 
little script created instead of a symlink.

Who creates the symlink when a RPM containing a new service is 
installed? Is it done by a `ln' command in the RPM's post-install 
script, or does the post-install script call another script to actually 
create the link? If it's the latter, we could hijack the script it calls 
to create our little script instead of a symlink.

> 2. Include the openssi enhanced RH/FC service command in the aaa_base 
> rpm, and tell users to use that to start services.

I like this, because it makes it easier to keep this feature in sync 
between the FC2 and SuSE branches. It does depend, however, on getting 
SuSE users to do something that only RH/FC users are used to doing, 
which is a drawback.

> 3. A hybrid of the two above, include the service command, and replace 
> the /sbin/rc* links with scripts which call their /etc/init.d scripts 
> through service.

Hmm... I like this even better than option 2, assuming we can solve the 
problems of option 1.

> Any comments/suggestions/preferences? Especially people who are more 
> familiar with SuSE administration.

Yes, please speak up if you're familiar with SuSE system administration. 
Most of the core OpenSSI developers primarily use Fedora and Red Hat, so 
any decisions we make on our own will be influenced by that bias.

For those of you who don't understand this aspect of OpenSSI, merely 
calling an /etc/init.d/<service> script will just start or stop a 
service on a single node. To take advantage of our clusterwide RC script 
system on Red Hat or Fedora, you need to control services via Red Hat's 
`service' command. This avoids the need for us to modify every 
/etc/init.d/<service> script. The question is what should we do on SuSE, 
since it doesn't have a `service' command.

Regards,

Brian