[Bug 1492546] Re: Systemd runs ifdown on shutdown even when it shouldn't

Martin Pitt martin.pitt at ubuntu.com
Tue Jan 12 20:23:20 UTC 2016


These units moved to ifupdown in the meantime, moving component. There
is now a fix for this, by adding Slice=system.slice to ifup at .service.

** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 systemd package in Debian:
  Fix Released

Bug description:
  The unit /lib/systemd/system/ifup at .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 at .service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1492546/+subscriptions



More information about the foundations-bugs mailing list