touch-packages team mailing list archive

[Alkis Georgopoulos <1492546@xxxxxxxxxxxxxxxxxx>]

> ifupdown should not have a config stanza (or at least only a manual
one) for this.

Hi Martin, yup, when network manager was introduced in Ubuntu I've had added code to LTSP to dynamically put "iface $DEVICE inet manual" in /etc/network/interfaces, to prevent network manager from assigning an IP to it, breaking netboot.
An empty line didn't do the trick, "manual" was necessary.

I'll test and leave feedback when systemd 0.8.8ubuntu1 reaches the
repositories.

Thanks a lot for your work in this!

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