I've seen this as well on my desktop. For me it was not a regression
vs. upstart (there are bug reports about nfs mounts similarly not being
mounted at boot under upstart in Ubuntu 14.10 and later), which is why I
did not consider this a blocker for switching by default.
Looking at the systemd mount generator output on my system, I see entries such
as:
$ cat /run/systemd/generator/srv.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
What=<server>:/
Where=/srv
Type=nfs4
Options=soft,intr,async,nolock,sec=krb5i,proto=tcp
$
This is notably lacking any dependency information requiring the network
to be up before trying (and failing) to start the unit.
Reassigning to systemd.
** Package changed: nfs-utils (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1429975
Title:
nfs no longer mounted at boot with systemd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429975/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
