From owner-freebsd-questions Tue Aug 28 21: 2:17 2001 Delivered-To: freebsd-questions@freebsd.org Received: from itouch.co.nz (itouch.co.nz [203.99.66.188]) by hub.freebsd.org (Postfix) with ESMTP id 2A8E837B408 for ; Tue, 28 Aug 2001 21:02:14 -0700 (PDT) (envelope-from jonc@itouch.co.nz) Received: (from jonc@localhost) by itouch.co.nz (8.11.3/8.11.1) id f7T41wW22267; Wed, 29 Aug 2001 16:01:58 +1200 (NZST) (envelope-from jonc) Date: Wed, 29 Aug 2001 16:01:58 +1200 From: Jonathan Chen To: Matthew Emmerton Cc: freebsd-questions@FreeBSD.ORG Subject: Re: getting nat to refresh its rules Message-ID: <20010829160158.A21946@itouchnz.itouch> References: <001301c13037$64fad820$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001301c13037$64fad820$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Tue, Aug 28, 2001 at 11:04:59PM -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Aug 28, 2001 at 11:04:59PM -0400, Matthew Emmerton wrote: [...] > Does anyone know of a way to get natd to re-read it's configuration file, > preferably without interrupting any sessions that are in progress? I tend to use a `kill -9 natd-pid && /sbin/natd -f ....'. I find that if you don't use a `kill -9', natd hangs around just long enough to not come up right-away. You may lose a few packets, though.. -- Jonathan Chen ---------------------------------------------------------------------- The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message