touch-packages team mailing list archive

[Alkis Georgopoulos <1492546@xxxxxxxxxxxxxxxxxx>]

Well...

This is *not* needed anymore, i.e. the current bug was solved:
# sed '/^ExecStop=/d' -i /lib/systemd/system/ifup@.service

Unfortunately now this is needed, i.e. the same bug appeared elsewhere:
# sed '/^ExecStop=/d' -i /lib/systemd/system/networking.service

The networking.service file now got an unconditional ifdown command:
$ grep ExecStop /lib/systemd/system/networking.service  
ExecStop=/sbin/ifdown -a --read-environment

Wouldn't it be easier to create a small.... "careful-ifdown"  script,
that borrows code from /etc/init/networking.conf, and have all the
.service and init files call that one instead?

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