Ubuntu
ifupdown package

  1. Bug #663352
  2. Comment #8

Comment 8 for bug 663352

Revision history for this message
uniomni (ole-moller-nielsen) wrote :

This bug also affects us on a Ubuntu 11.04 (64 bit) cluster
Here are some examples:

root@alamba:/client_filesystems/shared/home/install# service networking stop
stop: Unknown instance:
root@alamba:/client_filesystems/shared/home/install# service networking restart
restart: Unknown instance:
root@alamba:/client_filesystems/shared/home/install# service networking start
networking stop/waiting
root@alamba:/client_filesystems/shared/home/install# service networking stop
stop: Unknown instance:

If I use the (now deprecated?) init.d I get this:

 root@alamba:/client_filesystems/shared/home/install# /etc/init.d/networking restart
 * Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces
 * Reconfiguring network interfaces...

root@alamba:/client_filesystems/shared/home/install# /etc/init.d/networking start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service networking start

root@alamba:/client_filesystems/shared/home/install# /etc/init.d/networking stop
 * not deconfiguring network interfaces: network file systems still mounted.

The last error message is the first that might give me a hint that something else is happening, but it still looks like the original bug remains i.e. that the services networking command does not have restart and stop implemented.