In general it's done on an interface by interface basis. The commands ifdown and ifup are almost always used rather than /etc/init.d/networking. The init script itself just calls ifdown -a or ifup -a anyway. Debian never expects all interfaces to be altered in one shot unless you're on the console, and if you're remote that you have enough sense not to down the interface connected on.
Another way to do this after drastically editing /etc/network/interfaces would be to loop through "ifconfig down" (not ifdown*) for all interfaces, clear /etc/network/run/ifstate, then call ifup -a. * ifup/ifdown only work on interfaces exactly as they have been configured in the interfaces file. If the current state doesn't match the interfaces file then ifdown will refuse to down it. -- Brian On Mar 11, 2012, at 8:49 AM, Diego Zamboni <di...@zzamboni.org> wrote: > What is the recommended way of restarting networking after making changes in > Debian? That is the command you should execute then, instead of > "/etc/init.d/networking restart". > > I haven't used Debian in a while, but I can't believe you are expected to > stop network services before making any changes - it would make maintenance > very hard. > > --Diego > > On Mar 11, 2012, at 3:03 AM, Jimmy THRASIBULE wrote: > >> The problem is that Debian wants to avoid the use of >> `/etc/init.d/networking restart` >> >> Running /etc/init.d/networking restart is deprecated because it >> may not enable again some interfaces ... (warning). >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
