Your message dated Mon, 10 Mar 2008 21:18:57 +0100
with message-id <[EMAIL PROTECTED]>
and subject line bug closed in last version
has caused the Debian Bug report #468885,
regarding fireflier-server: Please add LSB formatted dependency info in init.d
script
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
468885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468885
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fireflier-server
Version: 1.1.6-2
Tags: patch
User: [EMAIL PROTECTED]
Usertags: missing-dependency
To be able to check boot script order, and also to be able to start
boot scripts in parallel, it is important to know the dependencies of
the various boot scripts. The Linux Software Base specifies a init.d
header file format useful for this purpose, and adding such header to
the anacron init.d script would make it possible for me to use this
information to check the current sequence and to speed up the debian
boot.
I am working on a system to update the boot sequence based on these
dependencies, and would like see this as the default in Lenny.
Because of this, it is nice if the dependencies was updated quickly.
<URL:http://refspecs.freestandards.org/LSB_2.1.0/LSB-generic/LSB-generic/initscrcomconv.html>
documents the LSB header format. Some debian notes are available from
<URL:http://wiki.debian.org/LSBInitScripts>.
Here is a patch to document the dependencies. I hope this is correct.
I was confused by the fact that update-rc.d is called with changed
sequence numbers, but did not find anything documenting why.
diff -ur fireflier-1.1.7.orig/debian/fireflier-server.init
fireflier-1.1.7/debian/fireflier-server.init
--- fireflier-1.1.7.orig/debian/fireflier-server.init 2007-07-27
18:02:29.000000000 +0200
+++ fireflier-1.1.7/debian/fireflier-server.init 2008-03-02
08:50:07.000000000 +0100
@@ -1,4 +1,11 @@
#! /bin/bash
+### BEGIN INIT INFO
+# Provides: fireflier-server
+# Required-Start: $remote_fs $syslog
+# Required-Stop: $remote_fs $syslog
+# Default-Start: 2 3 4 5
+# Default-Stop: 0 1 6
+### END INIT INFO
# fireflier startup script
# (=modified version of debian apache startup script)
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.
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Version: fireflier/1.1.7-4
This version adds the proposed section to the init script.
> 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.
I didn't add this change, as this way has unwanted sideeffects when
using some system to store the iptables rules (which is not by
fireflier).
I use the old iptables way for storing the rules on system shutdown and
restoring them on system boot.
As fireflier adds some rules on startup and removes them on shutdown
this would lead to some problems (like storing the fireflier-managed
rules)
I guess others use similar mechanisms.
Martin
signature.asc
Description: This is a digitally signed message part
--- End Message ---
