Newsgroups: news.software.b
Path: utzoo!henry
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: Odd expire output
Message-ID: <1990Jul12.151917.20244@zoo.toronto.edu>
Organization: U of Toronto Zoology
References: <1990Jul9.183558.287@caen.engin.umich.edu> <1990Jul10.022506.23924@zoo.toronto.edu> <1990Jul12.062819.20760@pegasus.com>
Date: Thu, 12 Jul 90 15:19:17 GMT

In article <1990Jul12.062819.20760@pegasus.com> richard@pegasus.com (Richard Foulk) writes:
>>The fix is to go find the messed-up line(s) in your history file,
>>and either tidy them up or get rid of them.
>
>Won't this blow away the dbm stuff?  I thought the only safe thing
>to do was rebuild the history files from scratch when things got
>messed up.  (?)

Mm, I should have mentioned this.  You can rebuild the dbm/dbz database
without having to rebuild the history file from scratch.  At the moment
(this is subject to change), the procedure is to lock the news system
(e.g. with locknews), cd /usr/lib/news, and "mkdbm history".  (Mkdbm can
be found in /usr/lib/newsbin/expire, if nowhere else.)
-- 
NFS:  all the nice semantics of MSDOS, | Henry Spencer at U of Toronto Zoology
and its performance and security too.  |  henry@zoo.toronto.edu   utzoo!henry