roy@phri.UUCP (Roy Smith) (01/19/88)
The past few days I've noticed something new. If I suspend rn, do
some stuff, and start rn up again, sometimes I get:
rn read error: Not owner
caught an internal error -- .newsrc restored
I think I got the error messages right; I'm doing this from memory.
I've noticed that rn has another subtle bug with signal handling; if you
start up rn on a busy system and suspend it before it finishes the initial
newsgroup scan, it will (sometimes?) hang when you bring it back into the
foreground. Has anybody else seen these bugs?
We've got "$Header: rn.c,v 4.3.1.3 85/05/16 16:47:10 lwall Exp $"
and news 2.11.14 (yes, I know our rn is somewhat out of date). This is all
on a MtXinu 4.3 BSD/NFS VAX. Our rn binaries predate the 4.3 upgrade; I
don't remember exactly but they were probably compiled on a fairly vanilla
4.2 system.
--
Roy Smith, {allegra,cmcl2,philabs}!phri!roy
System Administrator, Public Health Research Institute
455 First Avenue, New York, NY 10016