On 2011-04-04 11:39 +0200, Jamie Heilman wrote:
> rpcbind carps about things that it probably shouldn't on boot,
> specifically:
>
> rpcbind: Cannot open '/var/run/rpcbind/rpcbind.xdr' file for reading, errno 2
> (No such file or directory)
> rpcbind: Cannot open '/var/run/rpcbind/portmap.xdr' file for reading, errno 2
> (No such file or directory)
Having just switched from portmap to rpcbind, I find these messages
rather annoying.
> If the intent was to persist those state files across reboots, then
> putting them in /var/run was a bad idea, seeing as that gets cleaned
> out on boot automatically.
I don't think this was the idea; rather, the state needs to preserved if
rpcbind is restarted while the system is running (e.g. when the rpcbind
package is upgraded).
> As it is now, with -w being passed to
> rpcbind the above messages are always going to appear on boot.
Since it is not really an error if the files do not exist (rpcbind will
perform a normal start instead of a warmstart), how about patching them
out?
Regards,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
