Alkis Georgopoulos [2016-01-13 8:47 -0000]: > An empty line didn't do the trick, "manual" was necessary.
Ah, that's good. "manual" should indeed keep NM from touching it, but current ifupdown should also not tear down "manual" interfaces on shutdown. So in theory, with 0.8.8ubuntu1 your shutdown should be good now. Confirming this would be really helpful. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1492546 Title: Systemd runs ifdown on shutdown even when it shouldn't Status in ifupdown package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Invalid Status in ifupdown 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/ifupdown/+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
