From owner-freebsd-isp Thu Aug 15 09:39:24 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21087 for isp-outgoing; Thu, 15 Aug 1996 09:39:24 -0700 (PDT) Received: from glycerine.mulberry.com (jasonw@glycerine.mulberry.com [204.187.141.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA21072 for ; Thu, 15 Aug 1996 09:39:20 -0700 (PDT) Received: by glycerine.mulberry.com id AA26930 (5.67b/IDA-1.5 for freebsd-isp@FreeBSD.ORG); Thu, 15 Aug 1996 12:43:56 -0400 Date: Thu, 15 Aug 1996 12:43:56 -0400 (EDT) From: Jason Wilson To: Joe Greco Cc: Craig Harding , freebsd-isp@FreeBSD.ORG Subject: Re: INN In-Reply-To: <199608151530.KAA13822@brasil.moneng.mei.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 15 Aug 1996, Joe Greco wrote: > > Jason Wilson wrote: > > > > >After starting INN everything runs smoothly; feeds come in/go out fine, nnrp > > >clients connect and read/post fine etc etc. After running for about > > >15-30 minutes everything stops. All incoming and outgoing nntp feeds > > >close, nnrp clients hang, ctlinnd hangs, and when I telnet to > > >the nntp port it times out with dest unreachable. From a ps listing > > >everything looks normal. Everything was working fine until I reinstalled > > >FBSD a few days ago. > > > > Just a thought - did anything happen to your swap configuration or similar > > when you reinstalled FreeBSD? INN keeps everything in memory and grows to be > > a very large process. In my configuration it starts out at around 2MB at > > boot-time and slowly grows over the next hour or so to 6-7MB. This could > > interact with a swap or memory problem with the result you describe. > It starts at around 2MB, goes upto about 8MB within an hour or so, then sits at around 11MB thereafter. I haven't really put it to any use other than one incoming feed (ie. there's no nnrp clients yet) due to the performance problems. As for swap though it sits quite low. The ram will go from (24MB current) to 64MB after this issue is resolved. The only time I see any real performance is in the first minute before any incoming feeds start. Suggestions? Jason