On Thu, Mar 06, 2008 at 08:20:36AM +0100, Petter Reinholdtsen wrote: > Here is a patch to document the dependencies. I hope this is correct. > > diff -ur ircd-irc2-2.11.1p1+dfsg.orig/debian/ircd-irc2.init > ircd-irc2-2.11.1p1+dfsg/debian/ircd-irc2.init > --- ircd-irc2-2.11.1p1+dfsg.orig/debian/ircd-irc2.init 2008-03-06 > 07:56:05.000000000 +0100 > +++ ircd-irc2-2.11.1p1+dfsg/debian/ircd-irc2.init 2008-03-06 > 08:19:41.000000000 +0100 > @@ -1,7 +1,12 @@ > #!/bin/sh > -# > -# Starts/stops the irc daemon > -# > +### BEGIN INIT INFO > +# Provides: ircd-irc2 > +# Required-Start: $remote_fs $syslog > +# Required-Stop: $remote_fs $syslog > +# Default-Start: 2 3 4 5 > +# Default-Stop: 0 1 6 > +# Short-Description: Starts/stops the irc daemon > +### END INIT INFO
The daemon itself isn't using syslog, so that shouldn't be needed. (The ircdwatch binary is, but that's not started.) I guess that $remote_fs implies that all filesystems should be available, that network is up and that I have a resolver (/etc/resolv.conf)? It will read /etc/resolv.conf when starting, open it's config files, open it's logs files in /var/log/ircd/, read /var/run/ircd/ircd.tune. > As the stop script do not seem to do much except killing the daemon, > that task might be better left to the sendsigs script in runlevel 0 > and 6, to speed up shutdown. If this is indeed the case, I recommend > removing 0 and 6 from the Default-Stop list. It does a few things when receiving a sigterm: - Send to all other servers that it's being killed - Close the log files. - Write it's tune file. - Tries to send whatever it still has in it's queues - And dies Nothing is really that important. It can perfectly be killed by the sendsigs script. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
