From owner-freebsd-questions Tue Nov 23 12:59:23 1999 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 75606153D9 for ; Tue, 23 Nov 1999 12:59:05 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 11qLoN-0006Q2-00; Tue, 23 Nov 1999 19:41:11 +0000 Date: Tue, 23 Nov 1999 19:41:11 +0000 From: Ben Smithurst To: Joseph Lee Cc: freebsd-questions@freebsd.org Subject: Re: natd restarting remotely Message-ID: <19991123194111.B2126@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joseph Lee wrote: > Is there a graceful way to restart natd remotely such as say with a HUP? > > I've tried killall natd; natd -f natd.rc, but that just started up a > second natd while the first 1 hadn't died yet. > > Maybe killall -9 natd; natd -f natd.rc? Have you tried something like `killall natd; sleep $n; natd -f natd.rc` for some value of n which would probably allow the first natd to die? I don't use natd, so I don't even know if it responds to SIGTERM, so forgive me if this is a silly suggestion. SIGKILL should *really* be a last resort. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message