No network when docking

Karl Auer kauer at biplane.com.au
Wed Oct 8 15:12:54 UTC 2014


On Wed, 2014-10-08 at 07:50 -0700, NoOp wrote:
> again is to issue 'sudo killall NetworkManager'. See:
> [...]
> Which is effectively the same thing as 'sudo killall NetworkManager' -

Hm. You are quite right; I saw "killall" and just thought "OK, NM dead,
now poor OP has no NM and nothing to replumb his network" but of course
upstart respawns NM if you kill it. So killing it really is the same as
restarting it.

Even so, I think the right instruction is "sudo restart
network-manager". The command better reflects what is actually
happening, and it leaves the kill under the proper control of the
upstart system. About the only extra thing that killall would do is kill
multiple instances of NM, but NetworkManager won't run more than one
instance of itself. I guess if it was so broken that more than one
instance had managed to start, then killall would be the way to go...

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: EC67 61E2 C2F6 EB55 884B E129 072B 0AF0 72AA 9882
Old fingerprint: B862 FB15 FE96 4961 BC62 1A40 6239 1208 9865 5F9A






More information about the ubuntu-users mailing list