Package: portmap
Version: 6.0-6
Severity: important
Tags: patch
I believe the fix applied to fix the issues reported in #340158 and
#437912 actually broke runlevel 1 for portmap. In a normal boot where
NFS file system are to be mounted, portmap need to start in rcS.d, and
the call to the portmap script in rc2.d/ is a no-op. When switching
to runlevel 1, the portmap process is stopped, and when switching back
to runlevels 2-5, it need to be started again. Because of this, there
need to be start symlinks in runlevels 2-5 as well as the start
symlink in rcS.d/.
In short, I believe the bug reports and claims in #340158 and #437912
are wrong, and the portmap script actually need to run twice during
boot to make sure runlevel 1 works properly. And since the portmap
script was changed to not delay needlessly when called the second
time, there is not a big problem with boot speed to run it twice.
Here is a patch to reinsert the missing start symlinks during upgrade,
and make sure the correct symlinks are inserted on new installs not
using dependency based boot sequencing. The patch also bring the
init.d script header in line with the arguments used by update-rc.d.
diff -u portmap-6.0.0/debian/postinst portmap-6.0.0/debian/postinst
--- portmap-6.0.0/debian/postinst
+++ portmap-6.0.0/debian/postinst
@@ -7,7 +7,7 @@
CONFFILE=/etc/default/portmap
if [ "$1" = "configure" ] && [ -n "$2" ] &&
- dpkg --compare-versions "$2" lt 5-3; then
+ dpkg --compare-versions "$2" le "6.0.0-1"; then
err=$( update-rc.d -f portmap remove 2>&1 > /dev/null ) || {
echo "$err" >&2
exit 1
diff -u portmap-6.0.0/debian/rules portmap-6.0.0/debian/rules
--- portmap-6.0.0/debian/rules
+++ portmap-6.0.0/debian/rules
@@ -45,7 +45,7 @@
dh_installdebconf
dh_installdocs
dh_installexamples
- dh_installinit -- start 43 S . start 32 0 6 . stop 81 1 .
+ dh_installinit -- start 43 S 2 3 4 5 . start 32 0 6 . stop 81 1 .
dh_installcron
dh_installman
dh_installinfo
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
