James Mcpherson (firstname.lastname@example.org)
Tue, 9 Jun 1998 23:27:04 +1000 (GMT+1000)
On Tue, 9 Jun 1998, Ken Mitchelhill wrote:
> I decided to follow James MacPherson's lead that he mentioned last week
> about producing "clean" new htDig indices by deleting my old index before
> running rundig.
ObPedant - that's McPherson actually ;)
> My crontab looks like:
> 30 05 * * mon /home/kenm/abrf-www/htdig/bin/rundig
> 25 05 * * mon rm -f /home/kenm/abrf-www/htdig/db/*
> Trouble is that rundig doesn't seem to generate all the required files with
> the following error message generated:
> "Unable to read document index file
> Did you run htmerge?"
> Can anyone suggest where the problem might be?
I generally run rundig with the -v option which generates copious output.
As for your pathname, is that the actual path for your site's server? Also,
if that crontab entry above is your __personal__ crontab, is the dir that
rundig is dumping the data to owned by you or another user? If by you,
you should obviously check the perms on it! If it's not owned by you, are
you at least in the group which owns it and does the group have write
Any other suggestions in the magical world of dig?
-- I do not speak for the University of Queensland or the University Library J.McPherson@mailbox.uq.edu..au | this space _not_ for rent. email@example.com..au | remove erroneous char to reply properly
This archive was generated by hypermail 2.0b3 on Sat Jan 02 1999 - 16:26:32 PST