touch-packages team mailing list archive

[Bryan Quigley <bryan.quigley@xxxxxxxxxxxxx>]

Public bug reported:

Previously the consensus was that we don't support restarting the
networking service (due in part to events/upstart work).   (See
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1072518/comments/45
for the end result)

Is it supported now with systemd (15.04)?  The biggest (for the average
user) drawback previously was that it would bring down the entire
desktop thanks to dbus<->networking events.  The biggest issue for
server admins is that it might not bring up interfaces in the same way
as during boot.

Systemd:
$ sudo /etc/init.d/networking restart
[ ok ] Restarting networking (via systemctl): networking.service.

sudo service networking restart

Upstart: both were disabled.

If it's isn't supported, I think we need to disable them both again, and
recommend using ifup/down like previously.

If it is supported(-able) now, I'm happy to do a QA pass on it.. (and
we'll have some happier customers/users come 16.04)

** Affects: ifupdown (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: systemd-boot

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

Title:
  [systemd] Support networking restart?

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Previously the consensus was that we don't support restarting the
  networking service (due in part to events/upstart work).   (See
  https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1072518/comments/45
  for the end result)

  Is it supported now with systemd (15.04)?  The biggest (for the
  average user) drawback previously was that it would bring down the
  entire desktop thanks to dbus<->networking events.  The biggest issue
  for server admins is that it might not bring up interfaces in the same
  way as during boot.

  Systemd:
  $ sudo /etc/init.d/networking restart
  [ ok ] Restarting networking (via systemctl): networking.service.

  sudo service networking restart

  Upstart: both were disabled.

  If it's isn't supported, I think we need to disable them both again,
  and recommend using ifup/down like previously.

  If it is supported(-able) now, I'm happy to do a QA pass on it.. (and
  we'll have some happier customers/users come 16.04)

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