From owner-freebsd-hackers Fri Oct 6 1:19:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id BF38137B66F for ; Fri, 6 Oct 2000 01:19:22 -0700 (PDT) Received: (from root@localhost) by virtual-voodoo.com (8.11.1/8.11.1) id e968JLM47254 for freebsd-hackers@freebsd.org; Fri, 6 Oct 2000 03:19:21 -0500 (EST) (envelope-from steve) Date: Fri, 6 Oct 2000 03:19:21 -0500 (EST) From: Steve Ames Message-Id: <200010060819.e968JLM47254@virtual-voodoo.com> To: freebsd-hackers@freebsd.org Subject: IPFW quirk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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