🚀 go-pugleaf

news@teda.UUCP (Teraida Newsadm) wrote:
[experiencing abnormal exits from nnmaster]
} My solution is to run nnmaster from cron every 15 minutes. 

Are you sure you're still getting the entire database updated?  The only
time I had a problem with nnmaster exiting was when an article with an
extremely long "From:" header was received.  When this occurs, NO groups
past the group with the problem article are EVER updated until the article
expires.  Running nnmaster from cron only updates part of the database.
You can check this by looking in your nn/db/DATA directory to see if there
is a group of high-numbered files that do not have recent dates.

(BTW, did anyone read my article on how to track down the offending article
so that you could fix the article??  Did anyone find anything?)

If there is some other reason that nn is exiting (besides the From-header
bug that was fixed in usenet v6.3.6 and ftp v6.3.8), a crashing nnmaster
means that there is something else to be fixed.  Help Kim track it down
if you can.  Upgrade your nn if possible so you don't get stung by bugs
that have already been fixed.
-- 
Wayne Davison           \  /| / /| \/ /| /(_)    davison%drivax@uts.amdahl.com
davison@drivax.UUCP    (_)/ |/ /\| / / |/  \         ...!amdahl!drivax!davison