From 27ee79e565530cd8305ffd5531cf3bf80d5053db Mon Sep 17 00:00:00 2001 From: cjc Date: Fri, 8 Feb 2002 13:25:33 +0000 Subject: 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. --- etc/network.subr | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'etc/network.subr') 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 } -- cgit v1.1