Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!yale!ox.com!emv
From: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff)
Newsgroups: comp.archives
Subject: [news.software.b] Re: TRN problem
Message-ID: <1991Jan16.061339.12261@ox.com>
Date: 16 Jan 91 06:13:39 GMT
References: <SPIKE.91Jan14173043@world.std.com> <-!S+WW$@b-tech.uucp>
Sender: emv@ox.com (Edward Vielmetti)
Reply-To: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff)
Followup-To: news.software.b
Organization: Branch Technology
Lines: 30
Approved: emv@ox.com (Edward Vielmetti)
X-Original-Newsgroups: news.software.b

Archive-name: news/readers/trn/1991-01-15
Archive: ais.org:/pub/mthreads.c [141.211.206.16]
Original-posting-by: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff)
Original-subject: Re: TRN problem
Reposted-by: emv@ox.com (Edward Vielmetti)

>	For the third time trn has over flowed one of my disks
>writting:
>
><time stamp> ** interrupt 11 **
>
>to "mt.log".
>
>	Does anyone have a fix?  Previously it was suggested that this


There are two things (actually more) that need fixing.  One it to handle
sigsegv better and two is to remove any thread files that causes it 
(someone gave me this patch but I didn't save their name).
 
It's available via ftp from ais.org (pub/mthreads.c).

We need someone to go through and really fix some of these bugs with
mthreads and nntp.

There is also an occasional problem with mthreads (via nntp) getting groups
confused (ie, the database for one group actually applies to another).

-- 
Jon Zeeff (NIC handle JZ)	 zeeff@b-tech.ann-arbor.mi.us