Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!noose.ecn.purdue.edu!iuvax!purdue!haven!mimsy!nmrdc1!rdc30med
From: rdc30med@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: news.software.nntp
Subject: Re: Problem with 1.5.10
Message-ID: <1990Sep10.165114.19148@nmrdc1.nmrdc.nnmc.navy.mil>
Date: 10 Sep 90 16:51:14 GMT
References: <1990Sep6.172613.6568@nmrdc1.nmrdc.nnmc.navy.mil>
Distribution: na
Organization: Naval Medical Research & Development Command
Lines: 18

In article <1990Sep6.172613.6568@nmrdc1.nmrdc.nnmc.navy.mil> I wrote:
>
>[ wordy description deleted ]                            all the tmp files
>were still in ~/in.coming, none of the C-news batch files had been created.
>Not only that, but all the nntp sessions were still "active" although a
>netstat -a showed they were in CLOSE_WAIT.  Even after 7 hours they never

I think I have found part of the cause in addition to the SETPROCTITLE
problem Stan described.  I noticed via 'ps -ef | grep nntpd' that for each
nntp session started by my feed (and running as root), a second process 
running under "usenet" was spawned.  Since my news system is owned by user 
"news", this could be the problem.  Recompiling nntpd with POSTER defined as
"news" seems to have cured the above behavior.
-- 
Mike Dobson, Sys Admin for      | Internet: rdc30med@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30med
AT&T 3B2/600G Sys V R 3.2.2     | BITNET:   dobson@usuhsb.bitnet
WIN/TCP for 3B2                 | MCI-Mail: 377-2719 or 0003772719@mcimail.com