🚀 go-pugleaf

Aaron Hughes writes
> Ok - this is really starting to bug me.  I have made no
> changes whatsoever to my system.  I started up NG yesterday
> and after ~30 seconds it quits.  It perfoms fine, but 
> quits after about 30 secs - it lets me read news and the usual,
> but dies.  Any hints? I have changed nothing anywhere for a 
> while, so I don;t think it was anything I did.
> 
You might want to check the disk that the news articles are stored  
on...I've got a semi-flakly harddrive that has a few bad sectors on it and  
if NewsGrazer trys to read a file sitting on one of them, it'll bomb with  
no warning.

To check and see if this is the case you could try something like in a  
Stuart or Termial window:

find ~news -name "*" -print | xargs -i cat {} /dev/null 1> /dev/null 2>  
~/junk

That should give you a list of bad files in the file 'junk', your mileage  
may vary, I use zsh, so your syntax may be a bit different depending on  
the shell you use...This will take awhile to run (on my machine, a 25Mhz  
040, and a ~news directory size of 25 megs, it took a little over an hour)   
If anyone knows of a better way to do this, I'd love to hear it.
-- 
Jeff Cooper
NeXTmail: cooper%midkemia@plains.nodak.edu
	  uunet!plains!midkemia!cooper