makehistory in crontab (LINUX)
Russ Allbery
rra at stanford.edu
Wed Apr 26 20:37:06 UTC 2000
Chris Loos <c.loos at dizag.de> writes:
> I configured INN under LINUX and it is working quit well.
> And I added a cronjob as I found in a FAQ:
> # check the history database from time to time
> # date: every tuesday morning 04:00am
> 0 4 * * 2 news /usr/lib/news/bin/makehistory -buv
You should never need to do this. makehistory should only be run when
setting up a brand new server or when recovering from a crash that
corrupted the history or overview. (I'm not sure why a FAQ would
recommend the above; even in the olden days of INN 1.x, one generally just
ran expireover -a to handle missing overview entries.)
> When this job ran this week the first time, I got an email telling me that
> innd is not running.
Yeah, innd doesn't like the history file changing out from under it.
You should be able to just remove that cron job completely.
--
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the inn-workers
mailing list