news@linac.fnal.gov (07/24/90)
Machine: Sun 4/260c, SunOS 4.0.3, B News 2.11.19, NNTP 1.5.9 Ever since I got our NNTP link up and running several days ago, article numbers are are no longer consecutive in any of the articles received via NNTP. This was never a problem when only UUCP was being used to receive the news. So now when someone fires up rn they see ridiculous messages like >> Unread news in comp.unix.questions 2393898 articles when in fact there are only five articles in ~/news/comp/unix/questions. An ls reveals that the actual article numbers are:2,39,239,3939,23939 . Also rn gives out "Warning: someone reset XX.XX.XX - assuming nothing read" messages on startup. I assume these problems with rn are just due to the non-consecutive article numbers. Also I'm seeing a lot of >>inews: found bad ngsize 5313130 ng comp.sys.XXX, setting to 1 in /usr/lib/news/log and /usr/lib/news/errlog. Why is this happening? -------------------------------- | John Palkovic (708) 840-3527 | \ {tellab5,obdient}!linac!palkovic| |University of Wisconsin-Madison| FORTRAN: \ palkovic@linac.fnal.gov | | & Fermilab, Batavia, IL |Just say no.\ palkovic@fnal.bitnet |
palkovic@linac.fnal.gov (John A. Palkovic) (07/27/90)
A few days ago, I posted in this group about a problem I had with non-consecutive article numbers. It is fixed now, and I want to thank everyone who replied via email. I found the problem when I did an 'ls -l' on /usr/bin/rnews. Instead of a link to /usr/lib/news/inews, it was an executable file from an earlier installation of B news 2.11. I trashed it, made the link, and everything has been running smoothly since. Again thanks for the helpful replies.