Comment 17 for bug 1301015

It seems this was actually changed as of Ubuntu Saucy 13.10, as restart --system networking and /etc/init.d/networking both failed...

At this point, its faster/reliable to reboot my machine (10 seconds), than it is to open a terminal, and "ifdown --exclude=lo -a && sudo ifup --exclude=lo -a"..... init.d has always worked, including the many custom embedded Linux machines I develop for.

At least a better error message must be shown in the init.d output.