From owner-freebsd-security Fri Oct 13 23: 4:10 2000 Delivered-To: freebsd-security@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 7890B37B66C for ; Fri, 13 Oct 2000 23:04:08 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id B38881C76; Sat, 14 Oct 2000 02:04:07 -0400 (EDT) Date: Sat, 14 Oct 2000 02:04:07 -0400 From: Bill Fumerola To: cjclark@alum.mit.edu Cc: Milo Bloom , Peter Pentchev , redwards@meccamediagroup.com, freebsd-security@FreeBSD.ORG Subject: Re: Dynamic rc.firewall Message-ID: <20001014020405.D37870@jade.chc-chimes.com> References: <20001013131528.A17444@ringwraith.office1.bg> <5.0.0.25.2.20001013032255.00a8ee40@127.0.0.1> <20001013131528.A17444@ringwraith.office1.bg> <20001013132743.B17444@ringwraith.office1.bg> <3.0.5.32.20001013073440.009093f0@pop-server.cinci.rr.com> <20001013213431.T25121@149.211.6.64.reflexcom.com> <20001014010830.C37870@jade.chc-chimes.com> <20001013230128.V25121@149.211.6.64.reflexcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001013230128.V25121@149.211.6.64.reflexcom.com>; from cjclark@reflexnet.net on Fri, Oct 13, 2000 at 11:01:28PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 13, 2000 at 11:01:28PM -0700, Crist J . Clark wrote: > > Are /usr/bin/awk or /usr/bin/fgrep even available when rc.firewall gets called? > > > > Note my stress on calling them by their full path.. > > Yes, since the line in my old rc.firewall was literally, > > oip=`/sbin/ifconfig ${natd_interface} | /usr/bin/awk '/inet / { print $2 }'` Right. Rod caught my point that not everyone will have /usr at that time, so we should be doing it in a way that is compatable for NFS mounted /usr. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message