From owner-freebsd-net Sun Apr 23 11:29:26 2000 Delivered-To: freebsd-net@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id A95FE37B842 for ; Sun, 23 Apr 2000 11:29:23 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id MAA68164; Sun, 23 Apr 2000 12:30:16 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sun, 23 Apr 2000 12:30:15 -0600 (CST) From: Ryan Thompson To: Miguel Ruiz Cc: freebsd-net@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <39087384@MailAndNews.com> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Miguel Ruiz wrote to freebsd-net@FreeBSD.ORG: > Hey all: > > I was looking at this server, and it was generating a bunch of natd > processes. A bunch = 2 or 3? 20 or 30? 200 or 300? > 1000? In the first case (or two), I would suspect human error.. I.e., an administrator manually running too many natd processes where kill -HUP should be used. In the latter cases, I would suspect someone has created an automated script that was perhaps designed to keep natd running in the event it stopped, but their script obviously has some issues :-) > To the best of my memory there should only be one natd process > running. I tried to correct this and made a mistake and did a killall -9 > natd. This machine needs natd to be running or else it shut down all ip > interfaces. Oops. Nothing is hard coded all they have to do is reboot. The good news is if natd forces the link down for some reason, an ifconfig UP will generally reset it. > The problem is we need to find out why it was creating multiple natd > process. I've never witnessed this personally... Perhaps it was operator error? (Ran natd again instead of kill -HUP, or perhaps there is some homemade script that is responsible for the extra processes). > Does anyone know how 2 shutdown the xtra processes? You should be able to kill the extras individually by process ID, unless there are hundreds or thousands of them, in which case killall -9 natd IS the way to go. > thanx! > > M1k3 Virtually yours, - Ryan -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message