Xref: utzoo news.admin:14118 comp.bugs.misc:325 comp.sources.bugs:2904
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!fang!tarpit!bilver!bill
From: bill@bilver.uucp (Bill Vermillion)
Newsgroups: news.admin,comp.bugs.misc,comp.sources.bugs
Subject: Re: Trn help needed(again)
Message-ID: <1991May6.144006.5425@bilver.uucp>
Date: 6 May 91 14:40:06 GMT
References: <1991May3.195034.9911@bnlux1.bnl.gov>
Distribution: na
Organization: W. J. Vermillion - Winter Park, FL
Lines: 29

In article <1991May3.195034.9911@bnlux1.bnl.gov> abrams@dan.ccd.bnl.gov (The Ancient Programmer) writes:
 
>	Can anyone tell me what is happening here? Is Trn screwing up
>or has the news gone bad?  I'm running remote trn on a Sun4 (OS 4.1.1)
>using a Decstation 5000 as the news server.

Well I would suspect that some news article/directory is bad.

I had a similar occurance.  Mthreads would get to one point, and
stop and leave the rest unprocessed.

I ran mthreads with about 3 or 4 v's on the option line.  Each
extra v forces an extra level, and more output in the log.

When I found where the output of the log stopped, I checked that
group and found no problems.  So I looked at active 2 to find out
which newsgroup was to be processed next after the last one that was
processed.  When I went to that directory I found problems.

One I found was that instead of a file .threads I had a directory
called .threads.    I found one or two other corrupt portions
there.  Rm'd the offending files and directories and all was fine.

This may not be your problem, but it sounds similar.


-- 
Bill Vermillion - UUCP: uunet!tarpit!bilver!bill
                      : bill@bilver.UUCP