This bug was fixed in the package nfs-utils - 1:1.2.8-9ubuntu3
---------------
nfs-utils (1:1.2.8-9ubuntu3) vivid; urgency=medium
* Add 00git-start-statd-systemd.patch: Latest start-statd script from
1.3.2 to start rpc-statd.service under systemd.
* Add 23-systemd-pipefs_in_run.patch: systemd: Mount rpc_pipefs in /run
instead of
/var/lib/nfs/, like in the upstart units.
* Add 24-systemd-daemon-paths.patch: Adjust program paths in systemd units.
* debian/nfs-kernel-server.links: Add nfs-kernel-server.service alias
symlink, to match SysV init script.
* Add 25-systemd-server-before-client.patch: Order NFS server before client,
to make mounting NFS shares from localhost work reliably.
* Add debian/nfs-utils_env.sh: Translate our /etc/default files into runtime
configuration for nfs-config.service.
* debian/nfs-{common,kernel-server}.install: Install systemd units.
* debian/rules: Enable/start systemd units. (LP: #1312976)
-- Martin Pitt <martin.p...@ubuntu.com> Thu, 05 Mar 2015 07:46:41 +0100
** Changed in: nfs-utils (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1312976
Title:
Make NFS client/server work under systemd
Status in apparmor package in Ubuntu:
Fix Released
Status in nfs-utils package in Ubuntu:
Fix Released
Status in rpcbind package in Ubuntu:
Fix Released
Status in rpcbind package in Debian:
New
Bug description:
nfs-utils can not be used with systemd due to missing systemd unit or
init.d script.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1312976/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
