Path: utzoo!utstat!news-server.csri.toronto.edu!math.lsa.umich.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!samsung!uunet!mcsun!ukc!warwick!cudep
From: cudep@warwick.ac.uk (Ian Dickinson)
Newsgroups: news.software.b
Subject: Re: TRN problem
Message-ID: <1990Nov1.173628.22672@warwick.ac.uk>
Date: 1 Nov 90 17:36:28 GMT
References: <1990Oct25.112816.27533@warwick.ac.uk> <1990Oct26.094738.14905@warwick.ac.uk> <44*_H2&@b-tech.uucp>
Sender: news@warwick.ac.uk (Network news)
Organization: Team Limpid's Death Mollusc From Hell - The Good Old Boys
Lines: 34

In article <44*_H2&@b-tech.uucp> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
>>I tried killing mthreads and restarting it, and it all worked fine.
>>It had been running for a long time (999:99 with ps), so it may be hard
>>to recreate the problem.  But be warned - there may be a problem
>>with mthreads.  Sorry I can't offer any more info than this :-(
>While I doubt this is the problem, be sure to run "mthreads -e" now and
>then.

I run mthreads in daemon mode with the following options:

mthreads -v -a -d02 -e0500

This normally works fine.....

I forgot to mention in my previous article, that killing and restarting
didn't quite do the jobe properly....
mthreads noticed that there were new groups, but didn't thread them even
though I run with the -a option.
I fixed it with the following sequence:

mthreads -k
mthreads -f
mthreads -v -a -d02 -e0500

Whilst it was 'misbehaving' it also refused to follow the -d02 option,
and used the default -d10.  -d05 worked as advertised.  After restarting,
-d02 worked fine.

Strange times we live in seems....
--
\/ato.  Ian Dickinson.      GNU's feelin' horny.       Kunst und Wahnsinn.
vato@warwick.ac.uk                Sabeq.                  Mind the gap!
vato@tardis.cs.ed.ac.uk
gdd046@cck.cov.ac.uk            "I know what you sell - I don't want to buy!"