Package: rpcbind Version: 0.2.0-6 Followup-For: Bug #639849 I cam across this bug while tracking startup errors on my machine, so I guess it's the same thing as the original reporter wanted to point out.
By default rpcbind starts with the '-w' parameter, which makes it do a "warm start" by loading its statefile from /var/run/rpcbind. Since on my Wheezy machine /var/run is a symlink to /run which is a tmpfs, there is no statefile to be found. The temporary fix I made is I created an /etc/default/rpcbind file where i overrode the OPTIONS variable to "" (since I assume i'll never need warm restarts). For a proper fix I'd guess that the initscript should remove '-w' from the OPTIONS var if STATEDIR didn't exist (or lose the -w from the defaults altogether and ship an appropriately commented conf file for those who need it). Thanks. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rpcbind depends on: ii insserv 1.14.0-2.1 Tool to organize boot sequence usi ii libc6 2.13-16 Embedded GNU C Library: Shared lib ii libtirpc1 0.2.2-5 transport-independent RPC library ii libwrap0 7.6.q-21 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip rpcbind recommends no packages. rpcbind suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
