summaryrefslogtreecommitdiffstats
path: root/etc/network.subr
diff options
context:
space:
mode:
authorcjc <cjc@FreeBSD.org>2002-02-08 13:25:33 +0000
committercjc <cjc@FreeBSD.org>2002-02-08 13:25:33 +0000
commit27ee79e565530cd8305ffd5531cf3bf80d5053db (patch)
tree0d94060bfe0fc2951090b630d3f590714aaf0489 /etc/network.subr
parentfe2d1dffd326d27189f73fd3c69e407beecc937c (diff)
downloadFreeBSD-src-27ee79e565530cd8305ffd5531cf3bf80d5053db.zip
FreeBSD-src-27ee79e565530cd8305ffd5531cf3bf80d5053db.tar.gz
peter points out that we probably should not mess with the sysctl(8)
values at all if they are not purposefully set. What if the administrator messed with them in /etc/sysctl.conf? We don't want to overwrite them. If 'log_in_vain' is zero, do not force the issue. If it is non-zero, set it.
Diffstat (limited to 'etc/network.subr')
-rw-r--r--etc/network.subr9
1 files changed, 5 insertions, 4 deletions
diff --git a/etc/network.subr b/etc/network.subr
index 730c096..a3ec576 100644
--- a/etc/network.subr
+++ b/etc/network.subr
@@ -874,10 +874,11 @@ network_pass4() {
;;
esac
- [ "${log_in_vain}" -ne 0 ] && echo -n " log_in_vain=${log_in_vain}"
- sysctl net.inet.tcp.log_in_vain="${log_in_vain}" >/dev/null
- sysctl net.inet.udp.log_in_vain="${log_in_vain}" >/dev/null
-
+ [ "${log_in_vain}" -ne 0 ] && (
+ echo -n " log_in_vain=${log_in_vain}"
+ sysctl net.inet.tcp.log_in_vain="${log_in_vain}" >/dev/null
+ sysctl net.inet.udp.log_in_vain="${log_in_vain}" >/dev/null
+ )
echo '.'
network_pass4_done=YES
}
OpenPOWER on IntegriCloud