jon@savant.UUCP (Jon Gefaell) (08/05/90)
I'm hoping someone here can help.... savant runs ESIX SVR3 (Rev D) and B news 2.11 (fresh off of uunet ftp) With the exception of mail ([Rr]) everything seems to work peachy... Except... The /usr/lib/history.d and .od directories are taking up about 10+ megs now! The O'Reilly book says these files are self-trimming and reflect the articles currently on the system. Well, that doesn't seem right since there are about the same number of articles on the system as usual (I run expire regularly to keep articles from overflowing a 70M news file system) However, the history files grow, and grow, it's like Kudzu! Aarrgh! What can I do? Someone suggested I >1, >2, etc to make 'em 0 bytes and let the process start over. Of course, this doesn't take into effect two things 1.) They must be there for a reason, so nuking 'em might/should break some- thing. and 2.) It'll only happen again, it's hard to actually kill kudzu :) Can anyone help me out here. I'd hate to turn my news spool into a history archive... :) Also, there is another problem.... Expire seems very prone to die... It actually kept core dumping because a file had an 'invalid date' (1990July) and I had to use find to get the file and nuke it with an rn.... What is the problem here? Is this a known 'feature' :) or what? Also, I often get 'unable to write history file' (yeah, kudzu again) message back from cron (I've only gotten this message once running expire from the shell myself) Each time there seems to be sufficient disk space (but who knows) so I don't think it's not being able to make a temp copy of the history directories, but it very well may be that is what is goin on. Anyone have a clue on either of these? THANKS... Your help is much appreciated.