From owner-freebsd-isp Mon Aug 12 19:49:00 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA07167 for isp-outgoing; Mon, 12 Aug 1996 19:49:00 -0700 (PDT) Received: from netdev.comsys.com (COMSYS.COM [192.94.236.100]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA07155 for ; Mon, 12 Aug 1996 19:48:56 -0700 (PDT) Received: from 95server (ptp59.rof.net [206.168.17.59]) by netdev.comsys.com (8.6.12/8.6.9) with SMTP id UAA17859; Mon, 12 Aug 1996 20:59:46 GMT Message-ID: <320FDEB5.1BE7@comsys.com> Date: Mon, 12 Aug 1996 20:47:33 -0500 From: Alex Huppenthal Reply-To: alex@comsys.com Organization: Communication Systems Research Corp. X-Mailer: Mozilla 3.0b5aGold (Win95; I) MIME-Version: 1.0 To: Craig Harding CC: Jason Wilson , freebsd-isp@freebsd.org Subject: Re: INN References: <199608130119.SAA24256@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Craig Harding 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. > > -- C. > -- > Craig Harding Editor, Massey University Television Production Centre > "I don't know about God, I just think we're handmade" - Polly Check aliases of ip addresses. Check your dns records. Check your resolver. -Alex