From 978243bd80a17607addca02212af7e1aa7f4e8e0 Mon Sep 17 00:00:00 2001 From: John-Mark Gurney Date: Sun, 7 Sep 2003 07:52:56 +0000 Subject: make sure we really don't have a tty when installing rules. This prevents a flush command from asking a question (you can't see): If there is no tty associated with the process, this is implied. MFC after: 1 day --- share/examples/ipfw/change_rules.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'share/examples/ipfw') diff --git a/share/examples/ipfw/change_rules.sh b/share/examples/ipfw/change_rules.sh index 6ff163da3253..be7f7644064e 100755 --- a/share/examples/ipfw/change_rules.sh +++ b/share/examples/ipfw/change_rules.sh @@ -82,7 +82,7 @@ get_yes_no() { } restore_rules() { - nohup sh ${firewall_script} >/dev/null 2>&1 + nohup sh ${firewall_script} /dev/null 2>&1 rm ${TMPFILE} exit 1 } @@ -129,10 +129,10 @@ the ssh/telnet connection being used. if [ ${rules_edit} = yes ]; then nohup sh ${firewall_script} ${firewall_type}.new \ - > ${TMPFILE} 2>&1 + < /dev/null > ${TMPFILE} 2>&1 else nohup sh ${firewall_script}.new \ - > ${TMPFILE} 2>&1 + < /dev/null > ${TMPFILE} 2>&1 fi sleep 2; get_yes_no "Would you like to see the resulting new rules" -- cgit v1.2.3