I have always used network-manager, so I'll wait.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1429975
Title:
nfs no longer mounted at boot with systemd
Status in
Asked on upstream ML: http://lists.freedesktop.org/archives/systemd-
devel/2015-March/029226.html
In the meantime, you could edit /lib/systemd/system/remote-fs-pre.target
to append
Wants=network-online.target
After=network-online.target
This should fix the boot, at least if you use ifupdown
*** This bug is a duplicate of bug 1430280 ***
https://bugs.launchpad.net/bugs/1430280
Discussion on the ML confirmed that these *do* wait (implicitly) on
network-online.target. If you do systemctl show -p Wants -p After mnt-
server.mount you should see
Wants=network-online.target
In case this is helpful:
$ cat /run/systemd/generator/mnt-server.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=192.x.x.x:/opt/share
Where=/mnt/server
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
Indeed, these should have a Wants=/After=network-online.target.
** Tags added: systemd-boot
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
6 matches
Mail list logo
