On Tue, Jan 29, 2013 at 02:10:01PM -0000, Bogdan Stanciu wrote: > first, from the man, -w' Cause rpcbind to do a "warm start" by read a > state file when rpcbind starts up. The state file is created when > rpcbind terminates.
> therefore, the rpcbind throws a legitimate error when checking for non- > existing state files. now, either it checks for wrong files (then where > are the good ones) or the files should be there. > by running rpcbind stop, the files do get written to /run/rpcbind > folder. however, they disappear after reboot (not sure when). > so, IMHO, either the files never get written on shutdown, or they get > deleted sometimes between shutdown and boot (I doubt). The files are of course deleted between shutdown and boot. If the system is rebooted, it's no longer a warm start. That's why they're written to /run, which is not persistent across reboots. > if the -w option was meant to be there, niether the patch nor the > suppresion of the error message are valid solutions. I think -w being a separate option to rpcbind, and throwing a warning when the file is not found, are both silly and this should be corrected upstream, not worked around in the upstart job. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/835833 Title: spurious syslog error message because of use of -w on boot [rpcbind.xdr / portmap.xdr : errno 2 (no such file)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/835833/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
