Your message dated Wed, 26 Nov 2008 10:17:04 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#506429: fixed in portmap 6.0-9
has caused the Debian Bug report #506429,
regarding portmap init script doesn't work; uses pidofproc badly
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.)
--
506429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506429
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: portmap
Version: 6.0-8
Severity: important
Out of the frying pan, into the fire. The fix for #448470 isn't.
The way pidofproc is used in the portmap init script results in
stupidity during boot. As soon as the last interface is brought up,
/etc/network/if-up.d/mountnfs is executed and in turn it runs
/etc/init.d/portmap start (this happens before /etc/rcS.d/S43portmap
is run on my system). /etc/init.d/portmap fails because pidofproc
will fall back to using pidof -x unless you tell it not to. pidof -x
will see the /etc/init.d/portmap script in the process list and return
it's pid, which results in the portmapper and rpc.statd not being
started, which ultimately results in /etc/network/if-up.d/mountnfs
failing to do its job and none of my nfs mounts are brought up at boot
time.
Here's a hunk of the portmap init script with set -x turned on from my
boot log and ps aux | grep " $pid " thown into the if [ -n "$pid" ]
clause to show what pidofproc is actually finding:
Fri Nov 21 03:29:53 2008: Setting up networking....
Fri Nov 21 03:29:53 2008: Configuring network interfaces...
Fri Nov 21 03:29:53 2008: Starting portmap daemon...+ pidofproc portmap
Fri Nov 21 03:29:53 2008: + local pidfile line i pids= status specified pid
Fri Nov 21 03:29:53 2008: + pidfile=
Fri Nov 21 03:29:53 2008: + specified=
Fri Nov 21 03:29:53 2008: + OPTIND=1
Fri Nov 21 03:29:53 2008: + getopts p: opt
Fri Nov 21 03:29:53 2008: + shift 0
Fri Nov 21 03:29:53 2008: + base=portmap
Fri Nov 21 03:29:53 2008: + [ ! ]
Fri Nov 21 03:29:53 2008: + pidfile=/var/run/portmap.pid
Fri Nov 21 03:29:53 2008: + [ -n /var/run/portmap.pid -a -e
/var/run/portmap.pid ]
Fri Nov 21 03:29:53 2008: + [ -x /bin/pidof -a ! ]
Fri Nov 21 03:29:53 2008: + status=0
Fri Nov 21 03:29:53 2008: + /bin/pidof -o %PPID -x portmap
Fri Nov 21 03:29:53 2008: + [ 0 = 1 ]
Fri Nov 21 03:29:53 2008: + return 0
Fri Nov 21 03:29:53 2008: + pid=1185
Fri Nov 21 03:29:53 2008: + [ -n 1185 ]
Fri Nov 21 03:29:53 2008: + ps aux
Fri Nov 21 03:29:53 2008: + grep 1185
Fri Nov 21 03:29:53 2008: root 1185 0.0 0.0 1708 520 tty1 S+
03:29 0:00 /bin/sh -x /etc/init.d/portmap start
Fri Nov 21 03:29:53 2008: + log_begin_msg Already running.
If you make the pidofproc call a bit more sane, this problem won't
occur. Use $(pidofproc -p /var/run/portmap.pid /sbin/portmap) and
it should work just fine.
--
Jamie Heilman http://audible.transient.net/~jamie/
"...thats the metaphorical equivalent of flopping your wedding tackle
into a lion's mouth and flicking his lovespuds with a wet towel, pure
insanity..." -Rimmer
--- End Message ---
--- Begin Message ---
Source: portmap
Source-Version: 6.0-9
We believe that the bug you reported is fixed in the latest version of
portmap, which is due to be installed in the Debian FTP archive:
portmap_6.0-9.diff.gz
to pool/main/p/portmap/portmap_6.0-9.diff.gz
portmap_6.0-9.dsc
to pool/main/p/portmap/portmap_6.0-9.dsc
portmap_6.0-9_amd64.deb
to pool/main/p/portmap/portmap_6.0-9_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anibal Monsalve Salazar <[EMAIL PROTECTED]> (supplier of updated portmap
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 26 Nov 2008 20:14:15 +1100
Source: portmap
Binary: portmap
Architecture: source amd64
Version: 6.0-9
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Description:
portmap - RPC port mapper
Closes: 448470 506429
Changes:
portmap (6.0-9) unstable; urgency=medium
.
* In both init.d and postinst, replace "pidofproc portmap" with
"pidofproc -p /var/run/portmap.pid /sbin/portmap";
closes: #448470, #506429
Checksums-Sha1:
9a18962fa344c5e423562ef20ee325eb39a063f7 1049 portmap_6.0-9.dsc
719126a4ef594eb4d2efb7c1b392c7e17d62e835 25819 portmap_6.0-9.diff.gz
132daad6300b18c2518b4d5d6e7e5db1740c1235 37318 portmap_6.0-9_amd64.deb
Checksums-Sha256:
60f8883e47b1876d479c38b05c3c009dcfc619bccd1433b8abfacea02d533f09 1049
portmap_6.0-9.dsc
7a51a800d652608cb6c197c951bd75536f6cff6b6e1e2718aca199253ffb61ee 25819
portmap_6.0-9.diff.gz
18dfc408e53b9eaf3e99730d012e7c38e9f85302684a52c224f3d13c8a0007d6 37318
portmap_6.0-9_amd64.deb
Files:
a47f0a290c7cd6b3b6027ab6f778278f 1049 net standard portmap_6.0-9.dsc
dbd605ad10295b22ad9bb9bfc4fe2b88 25819 net standard portmap_6.0-9.diff.gz
2ea40c4b4593778f0d30ddc91539a86d 37318 net standard portmap_6.0-9_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkktH7MACgkQgY5NIXPNpFUkaQCgph2dlMbmL/apA6VcUw7M1MZu
7DAAoM05AAkT/tJfts5g05jNI8rFHhVC
=+881
-----END PGP SIGNATURE-----
--- End Message ---
