From owner-freebsd-hackers Sat Oct 7 13:20: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 568A037B503 for ; Sat, 7 Oct 2000 13:19:49 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA90054; Sat, 7 Oct 2000 16:19:53 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sat, 7 Oct 2000 16:19:53 -0400 (EDT) From: Adam To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW quirk In-Reply-To: <200010060819.e968JLM47254@virtual-voodoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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