Yes, lxc-net is called lxc-net in all init systems where the job exists (syv, upstart, systemd)
Both lxc-net and network-manager need to be restarted (unless network-manager is smart and uses inotify to look for updates).
I don't believe containers would need to be restarted.
Yes, lxc-net is called lxc-net in all init systems where the job exists (syv, upstart, systemd)
Both lxc-net and network-manager need to be restarted (unless network-manager is smart and uses inotify to look for updates).
I don't believe containers would need to be restarted.