On Mon, May 01, 2006 at 09:47:28AM -0700, Russ Allbery wrote:
[...]
> > ### BEGIN INIT INFO
> > # Provides: skeleton
> > # Required-Start: $local_fs $remote_fs
> > # Required-Stop: $local_fs $remote_fs
> > # Default-Start: 2 3 4 5
> > # Default-Stop: S 0 1 6
> > # Short-Description: Example initscript
> > # Description: This file should be used to construct scripts to be
> > # placed in /etc/init.d.
> > ### END INIT INFO
>
> > Perhaps we should update the init script...
>
> Huh, I've not seen that before. I wonder if that's part of LSB, since it
> looks a little like the init script headers used in SuSE and Red Hat.
It's lsb.
Let me make up one for shishi-kdc (appended below).
I'd suggest keeping all the comments below the main block
to have the reasons somewhere.
Elrond
### BEGIN INIT INFO
# Provides: shishi-kdc
# Required-Start: $remote_fs $network $syslog $named
# Required-Stop: $remote_fs $network $syslog
# Default-Start: 3 4 5
# Default-Stop: S 0 1 2 6
# Short-Description: shishi-kdc - Kerberos Key Distribution Center (KDC)
# Description:
# Start/stop the kerberos authentication service
# main server, the Key Distribution Center (KDC)
### END INIT INFO
#
# Some comments about above choosing:
# At start:
# $remote_fs: So /usr and all other filesystems are there.
# $network: Probably better, when the interfaces are up.
# $syslog: So we can feed our important logs somewhere at startup.
# You want to know, why it's not starting, right?
# $named: So name resolution works.
# The above reasons mainly count for stop as well, so here some
# extra notes:
# $remote_fs: So we can close files cleanly.
# not $named: Well, I don't see any point in resolving names
# at stop-time.
_______________________________________________
Help-shishi mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-shishi
