On Wed, Jul 30, 2003 at 09:19:51AM +0100, Craig Genner <[EMAIL PROTECTED]> wrote:
> [...]
> Can I enquire as to why? I've never noticed you 'strongly discourage'
> this before.
How about "discourage, frequently" :-)
> I always thought that the service command just called the relevant script
> any way.
It does, but it calls the /etc/init.d/{$service} script. This means
it they won't take into account whether that service is enabled
or disabled in the configuration database.
If you look carefully at the scripts in /etc/init.d, you will see
that we tend to use them unmodified. This eases upgrade pain as we
don't have to maintain or modify these scripts.
However, the scripts in /etc/rc7.d/ are all links to e-smith-service.
The e-smith-service script checks the config db for the status of the
service in the config db before calling the relevant script in
/etc/init.d (if required).
So, if sshd is disabled in the config db and you call the
following scripts:
service sshd start # ssh starts
/etc/init.d/sshd start # ssh starts
/etc/rc7.d/S85sshd start # ssh will _not_ be started
Similarly for the action scripts in /etc/e-smith/events/*
Hmm, replacing /sbin/service with a link to
/etc/init.d/e-smith-service could remove this distinction, at the
cost of a small amount of maintenance...
Thanks,
Gordon
--
Gordon Rowell [EMAIL PROTECTED]
Director, Engineering
Mitel Networks Corporation http://www.mitel.com/
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org
