From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 28 07:10:12 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2AA816A4C2 for ; Thu, 28 Aug 2003 07:10:12 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CECF43FE0 for ; Thu, 28 Aug 2003 07:10:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h7SEABUp057028 for ; Thu, 28 Aug 2003 07:10:11 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h7SEABfM057027; Thu, 28 Aug 2003 07:10:11 -0700 (PDT) Date: Thu, 28 Aug 2003 07:10:11 -0700 (PDT) Message-Id: <200308281410.h7SEABfM057027@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Robert Watson Subject: Re: conf/56031: ipfw hangs on every invocation X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Robert Watson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2003 14:10:12 -0000 The following reply was made to PR conf/56031; it has been noted by GNATS. From: Robert Watson To: "James F. Hranicky" Cc: FreeBSD-gnats-submit@FreeBSD.org, admin@cise.ufl.edu, freebsd-bugs@FreeBSD.org Subject: Re: conf/56031: ipfw hangs on every invocation Date: Thu, 28 Aug 2003 10:07:55 -0400 (EDT) On Wed, 27 Aug 2003, James F. Hranicky wrote: > Upon upgrade to 4.8-STABLE #30: Tue Aug 12 11:51:33 EDT 2003, ipfw hangs each > time it is called. > > All my machines upgraded to the version above have ipfw's left hung by > /etc/periodic/security/500.ipfwdenied. > > Those still at 4.8-STABLE #28: Tue Jun 10 09:21:14 do not seem to have > this problem. > > I do not currently use ipfw on any machine for firewalling capabilities, it > is compiled into my kernel in case I need it. I have the default set to allow > all packets through. Could you send the output of "ps axlwww" showing the hung ipfw process, as well as its parent process? When you run ipfw on the command line using the same arguments found in the periodic script, does it hang? If so, what do you see when you press Ctrl-T? Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories