Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!usc!samsung!uunet!world!spike
From: spike@world.std.com (Joe Ilacqua)
Newsgroups: news.software.b
Subject: Re: trn: mthreads and 'interrupt 11'
Message-ID: <SPIKE.90Dec13112059@world.std.com>
Date: 13 Dec 90 16:20:59 GMT
References: <1990Nov19.175517.26757@src.honeywell.com>
	<1990Dec10.150638.16632@src.honeywell.com>
Sender: spike@world.std.com (Joe Ilacqua)
Organization: Software Tool & Die
Lines: 20
In-Reply-To: jkimball@SRC.Honeywell.COM's message of 10 Dec 90 15:06:38 GMT

In article <1990Dec10.150638.16632@src.honeywell.com> jkimball@SRC.Honeywell.COM (John Kimball) writes:

<Thanks to randy@chinet.chi.il.us (Randy Suess) and  Michael E. Dobson
><rdc30med@nmrdc1.nmrdc.nnmc.navy.mil> for their suggestions.  There were
<old .thread files lying about, owned by root.  Changing their ownership to
>news was insufficient;  I needed to rm them, then mthreads was happy.  (I
<didn't suspect that permissions could cause a segment violation problem.)

	The same thing just happen to me and it overflowed the disk
with 24 MB of:

Dec 13 10:34 ** interrupt 11 **

	This is a excellent answer to "Why run NN when there is TRN?".
'Cause 'nnmaster' has yet to f*ck me over where as 'mthreads' does it
all the time.

->Spike (In a ranting mood)
-- 
The World - Public Access Unix - +1 617-739-9753  24hrs {3,12,24,96,192}00bps