Aargh, I keep forgettnig about /var/log/upstart/!
It's not very informative:
$ sudo cat /var/log/upstart/statd.log
UPSTART_EVENTS =
Perhaps this is because statd came up fine when I started it manually,
some time after boot? I tried rebooting again, but the contents of that
file did not change.
$ cat /etc/default/nfs-common
# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid
alternatives
# for the NEED_ options are "yes" and "no".
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=
# Options for rpc.statd.
# Should rpc.statd listen on a specific port? This is especially useful
# when you have a port-based firewall. To use a fixed port, set this
# this variable to a statd argument like: "--port 4000 --outgoing-port
4001".
# For more information, see rpc.statd(8) or
http://wiki.debian.org/SecuringNFS
STATDOPTS=
# Do you want to start the gssd daemon? It is required for Kerberos mounts.
NEED_GSSD=
By the way it seems that am using NFSv4, which shouldn't need statd at
all according to that comment. My /etc/fstab contains
fridge:/home /home nfs auto,rw,hard,intr,_netdev
0 0
fridge:/stuff /fridge/stuff nfs auto,rw,hard,intr,_netdev
0 0
but when I 'sudo mount -a' to force NFS mounts, /proc/mounts lists these
as 'nfs4'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371564
Title:
statd fails to come up on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1371564/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
