Server admins have been restarting networking with init scripts for many years, and for me personally it was rather disturbing to find this no longer works -- as well as to read some of the comments here. Networking that cannot be reliably restarted in the same manner it's brought up at boot time is a major problem. Luckily the init scripts from 13.10 actually still work, so this is my current workaround.
I'm not really sure what someone might do with networking that cannot be manipulated with ifconfig and other lower level commands, and therefore properly managed with init/upstart, but whatever warnings need to be applied, perhaps should be applied to whatever that is. And the fact that some networking devices/configs may not be reliably reloaded/restarted should not restrict the functionality of those that can. In these various comments I've not heard a compelling reason one shouldn't be able to edit /etc/network/interfaces and restart/reload networking. Ubuntu Server has been my distro of choice for several years for colo servers, vps's, vm's, etc.. Perhaps it's time to look at a different server distro.. -- 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/1301015 Title: Networking does not restart Status in “ifupdown” package in Ubuntu: Opinion Bug description: In Ubuntu Server 14.04 it appears it is not possible to restart networking. This is fresh install from ISO. wirehive@ubuntu:~$ sudo /etc/init.d/networking restart wirehive@ubuntu:~$ echo $? 1 wirehive@ubuntu:~$ sudo service networking restart stop: Job failed while stopping start: Job is already running: networking wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart + PATH=/sbin:/bin + RUN_DIR=/run/network + IFSTATE=/run/network/ifstate + STATEDIR=/run/network/state + '[' -x /sbin/ifup ']' + '[' -x /sbin/ifdown ']' + . /lib/lsb/init-functions +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)' ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']' ++ . /lib/lsb/init-functions.d/20-left-info-blocks ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)' ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']' ++ . /lib/lsb/init-functions.d/50-ubuntu-logging +++ LOG_DAEMON_MSG= ++ FANCYTTY= ++ '[' -e /etc/lsb-base-logging.sh ']' ++ true + CONFIGURE_INTERFACES=yes + EXCLUDE_INTERFACES= + VERBOSE=no + '[' -f /etc/default/networking ']' + verbose= + '[' no = yes ']' + case "$1" in + init_is_upstart + '[' -x /sbin/initctl ']' + /bin/grep -q upstart + /sbin/initctl version + return 0 + exit 1 wirehive@ubuntu:~$ sudo bash -x service networking restart ++ basename service + VERSION='service ver. 0.91-ubuntu1' ++ basename service + USAGE='Usage: service < option > | --status-all | [ service_name [ command | --full-restart ] ]' + SERVICE= + ACTION= + SERVICEDIR=/etc/init.d + OPTIONS= + '[' 2 -eq 0 ']' + cd / + '[' 2 -gt 0 ']' + case "${1}" in + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']' + '[' 2 -eq 2 -a restart = --full-restart ']' + '[' -z '' ']' + SERVICE=networking + shift + '[' 1 -gt 0 ']' + case "${1}" in + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']' + '[' 1 -eq 2 -a '' = --full-restart ']' + '[' -z networking ']' + '[' -z '' ']' + ACTION=restart + shift + '[' 0 -gt 0 ']' + '[' -r /etc/init/networking.conf ']' + which initctl + grep -q upstart + initctl version + case "${ACTION}" in + stop networking stop: Job failed while stopping + : + exec start networking start: Job is already running: networking wirehive@ubuntu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
