Comments on continuing to provide support for RN/RRN

Dewey Henize dewey at sequoia.execu.com
Wed Dec 26 09:11:32 AEST 1990


]
]Tom,
]
]From your comment about mthreads I gather there's at least one other
]with problems making mthreads behave, at least ,other than myself.
]Like this other person, I've also had trouble reaching Wayne, basically
]for the same reason (i.e. mail gets bounced).
]
]....
]Here's my complaint:  mthreads periodically behaves in bizarre manner and
]completely fills the disk partition where the error log resides.  As you
]can imagine this causes a great deal of consternation at my site.  Further
]whilst exhibiting its strange behaviour, mthreads seems to be generating
]interrupts of its own which furthers exacerbates the problem.
]
I had a lot of trouble on both the machines I administer getting this 
started.  After a couple days fooling with it (thank goodness most of my
users had split for the holidays), I was able to track things down so far
as to determine it was apparently hanging forever (using CPU & I/O) trying
to get caught up or something on the junk directories.  They both had
huge numbers for the article numbers and they both had a lot of articles
in the directories as well.  I don't know that that is what the problem
was, but...
]....
]
]Now for the rest of you, while this message may appears to explicitly
]address Tom, it is really general a cry for help from any that can
]offer assistance.  Please e-mail me and I will summarize any/all
]responses that specifically offer a solution.
]
What I ended up doing was to mv the junk directories and remove them from
the active file, replacing the entry in the active file with a phone of
junk 000000 000000 y (however may zeros that was to match), and crank it up
one more time.  This time it got through fine and things have been cooking
along just fine since.

Whether the number of the articles was the culprit, the name/number that
junk had gotten up to, or some other factor that fell out in the wash I
honestly don't know at this point.  Nonetheless, it worked and now I'm
thoroughly hooked on trn - I find I actually get through with my newsreading
and still have some time left over to do what my company pays me for! :-)

I admit, though, that the ability to not even see some of the garbage posts
is really what makes me such a strong and vocal proponent. <grin>  Heck, I
can even get through the news heirarchy now!

]Thanks Tom for helping and Wayne for providing a basically decent
]replacement for rn.
]
Ditto and me too and all that!

]Regards,
]ger

Now, since I said this much, is there any way to have trn recognize 
crossposting at the thread selection level?  So that something like
the rn 'Jy' macro that kills across groups would be available?  I
*know* that it's working correctly now, and I'm not complaining really,
I'm just a tad spoiled by that old macro I got off the net and would
love to have the equivalent 'up' one level at threads instead of either
seeing the same crossposts or having to go into reading level to use
the 'Jy' to junk.

Hope this helps, and once again thanks to the authors for a neat and,
amazingly useful, package.

Dew
-- 
| Execucom and I often have different ideas.  THESE are mine, ok?  Ok.        |
|               dewey at execu.com or uunet!sequoia!dewey                        |
|Don't reword the question into such generality that it appears absurd, that's|
|a puerile trick.  -Barry Shein | But this IS Usenet!! - me                   |



More information about the Comp.sources.bugs mailing list