[news.software.b] Can I delete ohistory and nhistory after an expire, or what?

karl@sugar.uu.net (Karl Lehenbauer) (02/15/89)

I use the dbz routines with news 2.11 at patchlevel 14.

I have noticed that I end up having an ohistory file of about two meg and
an nhistory of a meg and a half or so and I was wondering if there was any
reason why I should keep these guys around -- I mean, I could always rebuild 
the history file if something happened to it.  

I tried to RTFM and didn't find anything.  Gurus, please pardon my naive 
question.
-- 
-- uunet!sugar!karl  | "Everyone has a purpose in life.  Perhaps yours is
-- karl@sugar.uu.net |  watching television."  -- David Letterman
-- Usenet BBS (713) 438-5018

karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) (02/16/89)

karl@sugar.uu.net (Karl Lehenbauer) writes:
   I use the dbz routines with news 2.11 at patchlevel 14.

   I have noticed that I end up having an ohistory file of about two meg and
   an nhistory of a meg and a half or so and I was wondering if there was any
   reason why I should keep these guys around

ohistory can usually be removed once expire(8) completes.  nhistory
should not exist after a successful completion of expire, however; at
the end of a successful expire, it is renamed as history.  If you
still have nhistory, you need to find something deeper wrong with
what's going on.

Cf. news/src/expire.c, approx lines 770-780.

--Karl

glee@cognos.uucp (Godfrey Lee) (02/21/89)

In article <KARL.89Feb15111702@triceratops.cis.ohio-state.edu> karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) writes:
+------
|karl@sugar.uu.net (Karl Lehenbauer) writes:
|   I use the dbz routines with news 2.11 at patchlevel 14.
|
|   I have noticed that I end up having an ohistory file of about two meg and
|   an nhistory of a meg and a half or so and I was wondering if there was any
|   reason why I should keep these guys around
|
|ohistory can usually be removed once expire(8) completes.  nhistory
|should not exist after a successful completion of expire, however; at
|the end of a successful expire, it is renamed as history.  If you
|still have nhistory, you need to find something deeper wrong with
|what's going on.
+------

nhistory after expire means that expire has died before finishing. I noticed
sometimes if I just rerun it, it would be okay, no idea why. Other times,
it indicates that the history file is corrupted, and you have to rebuild
the history file (use "expire -r"). I also noticed that the rebuild does not
expire articles (at least not all of them), and you have to do a regular
expire run after that to get everything up to snuff.

All in all, a lot of manual intervention and system resources. I am
just glad that this stuff will be replaced soon. Where is Cnews, where
is news 3.0 ?? I know, I know, it is coming Real Soon Now...

I am not complaining, just frustrated everytime I have to clean up, usually
right after I come back from a trip. Murphy is alive and well, sigh ...
-- 
Godfrey Lee                                            P.O. Box 9707
Cognos Incorporated                                    3755 Riverside Dr.
VOICE:  (613) 738-1338 x3802   FAX: (613) 738-0002     Ottawa, Ontario
UUCP: uunet!mitel!sce!cognos!glee                      CANADA  K1G 3Z4