touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

@Alkis: It's possible that this still affects Xenial even with fixing
ifup@.service, as networking.service (which does not do that network
file check any more) might also shut down the interfaces; it just does
it later on.

But this bears the question why on an LTSP system ifupdown has a
configuration for the interface that the root fs is mounted on? This
interface is being set up by the initramfs already, via udhcpd; ifupdown
should not have a config stanza (or at least only a manual one) for
this. How does this work? In particular, what's /etc/network/interfaces
and interfaces.d/* on that system?

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:
  In Progress
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