After an out-of-the-box installation of nfs-utils statd (started from nfsmount) fails to start due to a missing /var/lib/nfs/state. statd would normally create this file itself, but /var/lib/nfs is only writable for root and statd runs as nobody. The problem can be solved in one of two ways: (a) allowing nobody (or the root-group) to create files in /var/lib/nfs or (b) create an empty /var/lib/nfs/state during installation. The later seems more secure IMHO. This problem exists in nfs-utils-1.0.6-r6. I haven't tested with later versions, but it's not fixed in the ebuilds as far as I can tell.
Created attachment 93747 [details, diff] Creates /var/lib/nfs/state during installation This patch fixes the problem by creating /var/lib/nfs/state during installation. The patch has been made with nfs-utils-1.0.6-r6.
if you look at pkg_postinst(), you'll see that this is already taken care of
Comment on attachment 93747 [details, diff] Creates /var/lib/nfs/state during installation Sorry, I obviously didn't do my homework. This bug is actually a dublicate of #30486, which was resolved in 2004. I actually did have a problem with a missing /var/lib/nfs/state, but the problem must be somewhere else. Sorry for the inconvenience.
np, happens to everyone at some point
