From owner-freebsd-questions  Fri Apr 14 10:04:53 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id KAA25030
          for questions-outgoing; Fri, 14 Apr 1995 10:04:53 -0700
Received: from ns1.win.net (ns1.win.net [204.215.209.3])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA25024
          for <questions@freebsd.org>; Fri, 14 Apr 1995 10:04:51 -0700
Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id NAA00879 for questions@freebsd.org; Fri, 14 Apr 1995 13:06:37 -0400
From: Mark Hittinger <bugs@ns1.win.net>
Message-Id: <199504141706.NAA00879@ns1.win.net>
Subject: re: [2.0R] news server memleak?
To: questions@FreeBSD.org
Date: Fri, 14 Apr 1995 13:06:37 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1361      
Sender: questions-owner@FreeBSD.org
Precedence: bulk

> From: Faried Nawaz <fn@pain.csrv.uidaho.edu>
> 
> i've noticed a strange thing, though, and it puzzles me.  yesterday (18 day
> uptime) i noticed that the machine was living in swap.  it had innd running
> (ps said vsz was around 7.5mb), and had a few in.nnrpds running (ps said
> vsz for each was just over a meg).  i could not see how it all added up
> to > 20mb, but i was 10mb into swap.

There is at least one known file descriptor leak in innd 1.4sec2.  Here
is a patch for it:

This is a known problem. I got a fix some while ago (Sorry, so long ago
I forget where it came from - may have been direct from rsalz) and
patched it on to INN 1.4 here.  The relevant area, as kluged, now reads
(around line 82 in site.c):

    if (AmRoot)
        xchown(name);
    if (cp) {
if (cp->fd >= 0)
syslog(L_ERROR, "DEBUG ERROR SITEspool trashed:%d %s:%d", cp->fd, sp->Name, i);
        WCHANremove(cp);
        RCHANremove(cp);
        SCHANremove(cp);
        close(cp->fd);
        cp->fd = i;
        return TRUE;
    }
    sp->Channel = CHANcreate(i, CTfile, CSwriting, SITEreader, SITEwritedone);
    if (sp->Channel == NULL) {

I don't think this has made it into the current distribution.

There is another file descriptor leak in innd lurking someplace and I
haven't been able to track it down. 

See if this helps.

Regards,

Mark Hittinger
bugs@win.net