[Bug 1371564] Re: statd incompatible with /var as a separate filesystem

[Maciej Puzio]

For a system with a separate /var partition, the workaround from year 2010 
appears to work:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/525154/comments/8

For the Ubuntu 14.04 this workaround translates to:

--- /etc/init/statd.conf.ORIG   2013-09-11 16:46:50.0 -0500
+++ etc/init/statd.conf 2015-06-02 16:24:42.029659358 -0500
@@ -12,7 +12,7 @@
 # TYPE=nfs is handled in the "statd-mounting" job.
 #
 start on (started portmap ON_BOOT=
-  or (virtual-filesystems and started portmap ON_BOOT=y))
+  or (virtual-filesystems and mounted MOUNTPOINT=/var and started 
portmap ON_BOOT=y))
 stop on stopping portmap
 
 expect fork

-- 
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 incompatible with /var as a separate filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1371564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1371564] Re: statd incompatible with /var as a separate filesystem

[Marius Gedminas]

For the record, a sufficient workaround for me is to set NEED_STATD=no
in /etc/default/nfs-common, since NFSv4 doesn't need statd.

-- 
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 incompatible with /var as a separate filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1371564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs