Package: initscripts Version: 2.86.ds1-38 Severity: normal --- Please enter the report below this line. ---
According to my boot log, portmap (including rpc.statd) is started correctly by the init scripts: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Thu Jul 12 19:24:07 2007: DHCPOFFER from 192.168.0.1 Thu Jul 12 19:24:07 2007: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Thu Jul 12 19:24:07 2007: DHCPACK from 192.168.0.1 Thu Jul 12 19:24:07 2007: bound to 192.168.0.2 -- renewal in 45817 seconds. Thu Jul 12 19:24:08 2007: Starting portmap daemon.... Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: mount.nfs: rpc.statd is not running but is required for remote locking Thu Jul 12 19:24:09 2007: Either use "-o nolocks" to keep locks local, or start statd. Thu Jul 12 19:24:09 2007: done. Thu Jul 12 19:24:09 2007: Starting portmap daemon...Already running.. Thu Jul 12 19:24:09 2007: Waiting for /var/chroot/etch-ia32/home... It says (up there ^) that portmap is already running when it tries to start it a second time. It then sits there for a while before repeating the above messages. I'm not sure if it has a maximum number of retries, but I got bored and gave it a Ctrl-C. When it had finished booting, I went to text console (C-M-F1), logged in as root and tried this: # pidof portmap 1445 ...so portmap is definitely running. If at this point I do a # mount -a -t nfs ...then all of the NFS shares mount as they should, so it's not as if portmap has started and then hung. Anyway, I thought this might provide some useful diagnostics - I can run other tests if necessary. Tom --- System information. --- Architecture: amd64 Kernel: Linux 2.6.18.070406.1 Debian Release: lenny/sid 500 unstable thor 500 testing thor --- Package information. --- Depends (Version) | Installed ==================================================-+-================================ libc6 (>= 2.3.5-1) | 2.6-2 mount (>= 2.11x-1) | 2.12r-19 e2fsprogs (>= 1.32+1.33-WIP-2003.04.14-1) | 1.40.1-1 debianutils (>= 2.13.1) | 2.22.1 lsb-base (>= 3.0-6) | 3.1-23.1 sysvinit-utils | 2.86.ds1-38
signature.asc
Description: This is a digitally signed message part.
