🚀 go-pugleaf

Several users have complained about nnmaster dying.  There were
definitely bugs in the pre 6.3.6/6.3.8 versions which could cause the
master to dies, either because of articles with bad headers, or due to
network problems.

If you run 6.3.6, the "bad header" problem should be fixed (but it
still exists in 6.3.7! - get patch 8).  And with 6.3.10, most of the
network problems should be solved as well, so when

iand@labtam.oz (Ian Donaldson) writes:

>We found that if nnmaster was being run, connecting to the remote
>via NNTP, and the remote host dies, so does nnmaster.  It doesn't try
>and re-establish the NNTP link.

I believe this has changed with version 6.3.8.  We made some efforts
to have nnmaster detect immediately that the nntp server dies, and
just go to sleep immediately and wait for one -r period (you probably
don't use less than 10 minutes intervals to stay on good terms with
your NNTP server :-)

If this happened with 6.3.7 or later, I would certainly like to hear
about it.

And a small gripe:  When somebody reports a problem with nn, please
always mention the version, e.g. 6.3.7 meaning release 6.3, patchlevel 7.
It makes it much easier for me to distinguish between new and old bugs.
Thanks!

-- 
Kim F. Storm        storm@texas.dk        Tel +45 429 174 00
Texas Instruments, Marielundvej 46E, DK-2730 Herlev, Denmark
	  No news is good news, but nn is better!