Martin, I'm seeing a regression for this with systemd 228-2ubuntu1 in Ubuntu
Xenial.
Now I again have to remove the "ExecStop=/sbin/ifdown %I" stanza in order to
get netbooted clients to shut down.
Maybe something else is stopping the ifup service on shutdown now?
I tried to downgrade to the version shipped with Wily, but I was blocked by
some dependency issues.
** Changed in: systemd (Ubuntu)
Status: Fix Released => Triaged
--
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/1492546
Title:
Systemd runs ifdown on shutdown even when it shouldn't
Status in ltsp package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Triaged
Status in systemd package in Debian:
Fix Released
Bug description:
The unit /lib/systemd/system/[email protected] is Debian and Ubuntu specific,
it's not part of upstream systemd.
On shutdown, it unconditionally ifdowns all interfaces:
ExecStop=/sbin/ifdown %I
This is a regression from previous init systems (sysvinit and upstart)
which cared so that when a network file system was in use, they didn't
ifdown the interfaces.
Specifically, both /etc/init.d/networking and /etc/init/networking contain
these functions:
check_network_file_systems()
check_network_swaps()
which output the message "not deconfiguring network interfaces: network file
systems still mounted" and exit.
So, please call the same functions in the ExecStop= part of
[email protected].
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1492546/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
