Package:  portmap
Version:  5-19
Severity: important
Tags:     patch
User:     [EMAIL PROTECTED]
Usertags: incorrect-dependency

When testing dependency based boot sequencing, I discovered a problem
in the init.d script for portmap when installed with a provider of the
$named service.  Most (all?) providers of the $named service (I
discovered it with bind9 and lwresd), depend on $remote_fs, because
their binaries are located in /usr/, which is not guaranteed to be
available until after the scripts providing $remote_fs is done.
$remote_fs on the other hand depend on nfs-common, which in turn
depend on portmap, to make sure NFS is properly set up when used.  And
portmap in turn depend on $named, and there we have a dependency loop:

  $named->$remote_fs->nfs-common->$portmap->portmap->$named.

I propose to break this loop by dropping $named as a dependency for
portmap.  Portmap need to run before /usr/ is mounted when using NFS,
while at least bind9 need to run after /usr/ is mounted, so it make
sense for me to break the loop there.

I set severity to important, as this bug make it impossible to install
portmap when bind9 or lwresd is installed, and impossible to install
bind9 and lwresd when portmap is installed.

This patch solve the issues:

diff -ur portmap-6.0.orig/debian/init.d portmap-6.0/debian/init.d
--- portmap-6.0.orig/debian/init.d      2008-01-06 14:48:37.000000000 +0100
+++ portmap-6.0/debian/init.d   2008-01-06 14:50:49.000000000 +0100
@@ -6,8 +6,6 @@
 # Provides:          portmap
 # Required-Start:    $network
 # Required-Stop:     $network
-# Should-Start:      $named
-# Should-Stop:       $named
 # Default-Start:     S 2 3 4 5
 # Default-Stop:      0 1 6
 # Short-Description: The RPC portmapper

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.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to