Alkis, unfortunately rsyslog stops too early (before stopping
ifup@.service), the log shows no teardown of network at all. Not a
surprise with remote logging :-)
Is it possible for you to mount a local disk on /var/log/, enable
persistent journal (sudo install -d -g systemd-journal
/var/log/journal), reboot, and attach the previous journal with "sudo
journalctl -b -1 > /tmp/journal.txt"?
** Changed in: systemd (Ubuntu)
Status: Triaged => Incomplete
--
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:
Incomplete
Status in systemd package in Debian:
Fix Released
Bug description:
The unit /lib/systemd/system/ifup@.service 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
ifup@.service.
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
