diff options
| author | William Hubbs <w.d.hubbs@gmail.com> | 2013-02-11 09:45:14 -0600 |
|---|---|---|
| committer | William Hubbs <w.d.hubbs@gmail.com> | 2013-02-11 09:45:14 -0600 |
| commit | 5bfebbecea6514037ceef3b832660f70acf8a945 (patch) | |
| tree | 2c984e7669137555cb62ea6ee809040292fcc830 /init.d/network.in | |
| parent | 1280b97749ec60b4cd3f77d1c68202f305ad79b4 (diff) | |
Rename shutdown_network setting to keep_network
We were telling users that setting shutdown_network=YES would shut down
the network interfaces during shutdown, but this was exactly the
opposite of what we were doing. The default was YES, which was keeping
the interfaces active.
This keeps the default behavior, but renames the setting to keep_network
which more accurately describes its function, and instructs users to set
it to NO if they want the network interfaces to go down.
Diffstat (limited to 'init.d/network.in')
| -rw-r--r-- | init.d/network.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/init.d/network.in b/init.d/network.in index 6e9b8c1f..13895f0c 100644 --- a/init.d/network.in +++ b/init.d/network.in @@ -323,7 +323,7 @@ stop() # Don't stop the network at shutdown. # We don't use the noshutdown keyword so that we are started again # correctly if we go back to multiuser. - yesno ${shutdown_network:-YES} && yesno $RC_GOINGDOWN && return 0 + yesno ${keep_network:-YES} && yesno $RC_GOINGDOWN && return 0 local int= intv= cmd= downcmd= r= einfo "Stopping network" |