🚀 go-pugleaf

Vince Netz writes
> I upgraded to NS 3.0 a while back, and moved my .newsrc file and  
> NewsGrazer 72.3 to the new environment.  For the first 2 weeks or so, it  
> worked great.  Then intermittently at first, NewsG began to crash  
> without warning.  Cuz it happened infrequently I shrugged it off, but  
> last week it began crashing every time after running for about 15  
> minutes, sooner if I did any posting.  Today it crashed in about 3  
> minutes or less, and I couldn't even get a short post written.  Oh a  
> whim I deleted my .newsrc file, and viola it now runs perfectly (witness  
> this post!).  Has anyone else noticed this?  Does .newsrc get corrupted  

I have been using NG for years without any problem except for this past  
weekend.   My problem seems similar to what you are describing.  You can  
verify this by running netstat in a terminal window and looking at the NG  
receive queue- NG locks up when you get just over 1000 packets waiting.   
My solution was to remove all of the defaults for NG (using DefaultMgr or  
dremove), and simply restarting it and re-setting preferences.  Seems a  
little drastic- but I couldn't see what was wrong otherwise.  If you are  
reluctant to do this, first create a new account on your system and see if  
NG runs OK from the new user's directory- if it does, my fix should  
correct your problem.  

We have also had an intermittent problem with malformed posts that are  
only within out local domain.  Somehow these are allowed to propagate  
locally, but can't be read by newsgrazer- which crashes.  For these, I  
directly edit the .newsrc file to change the article count for the  
offensive newsgroup.

Jim
--
__________________________________________________________________
Jim Kiraly- jim@ljkiraly.lerc.nasa.gov- NASA Lewis Research Center
----------------- NeXT Mail preferred ----------------------------