[Petter Reinholdtsen] > This patch solve the issue: I just had a closer look, and discovered that the fam binary is in /usr/, and thus the script need to depend on $remote_fs, not $network. Here is a better patch:
--- /etc/init.d/fam.orig 2007-07-23 01:33:12.000000000 +0200 +++ /etc/init.d/fam 2007-12-31 20:39:16.000000000 +0100 @@ -1,10 +1,10 @@ #! /bin/sh ### BEGIN INIT INFO # Provides: fam -# Required-Start: $network portmap -# Required-Stop: $network portmap -# Default-Start: 1 2 3 4 5 -# Default-Stop: S 0 6 +# Required-Start: $remote_fs $portmap +# Required-Stop: $remote_fs $portmap +# Default-Start: 2 3 4 5 +# Default-Stop: 0 1 6 # Short-Description: File Alteration Monitor # Description: Debian init script for File Alteration Monitor ### END INIT INFO > As the stop script do not seem to do anything except killing the > daemon, that task might be better left to the sendsigs script in > runlevel 0 and 6. If this is indeed the case, I recommend removing 0 > and 6 from the Default-Stop list. This is still true. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
