touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Adjusting the Debian bug link, I discussed this on
https://bugs.debian.org/809166 already. ifupdown should *not* stop
"manual" interfaces with ifdown, unless you have an explicit "down"
action in /etc/network/interfaces. I assume this is not the case. It was
an explicit decision by the Debian maintainer (Guus) to not take these
"network file system" checks into the new .service, as this hides real
bugs and should really not be necessary.

So I take it the bug is now that "ifdown"ing a manual interface actually
"ifconfig down"s it?

** Bug watch added: Debian Bug tracker #809166
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809166

-- 
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