Date: Sat, 7 Oct 2000 16:19:53 -0400 (EDT) From: Adam <bsdx@looksharp.net> To: Steve Ames <steve@virtual-voodoo.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW quirk Message-ID: <Pine.BSF.4.21.0010071619140.37573-100000@turtle.looksharp.net> In-Reply-To: <200010060819.e968JLM47254@virtual-voodoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ha! I ran across that unfortunate symptom too and never figured out why it
worked for some users and not for others. Thanks! :) I ended up training
myself to use ipfw show instead.
On Fri, 6 Oct 2000, Steve Ames wrote:
>
>Hey... I just type 'ipfw -a list' on the command line and got back an
>invalid argument error. That confused me for a bit so I poked around
>for a while and then it just started working again. A bit more poking
>and I discovered that it fails if there is a file called 'list' in
>the directory the command is being executed from.
>
>Seems ipfw checks for a file containing commands before it checks to
>see if you've issued a valid command?
>
>A bit of experimenting ('touch flush', 'ipfw flush') seems to indicate
>that its true for most commands. Perhaps this is intentional but its
>behavior confused me a bit... And it means I can't leave a file called
>'list' laying around as then /etc/security output is wrong.
>
>-Steve
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010071619140.37573-100000>