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 [EMAIL PROTECTED]
>with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
