From: Douglas Kline <kline@he...> - 2004-04-22 17:33:27
> At 03:05 AM 4/22/2004, Rupert Jones wrote:
> >Hi Steve,
> >The directive to the db dir in rundig will override the value in the conf
> >Either that, or I've noticed some bizarre behaviour from ht://dig where the
> >values you choose during config time are the ones some of the applications
> >always use, no matter what your conf file says.
> Hey Rupert,
> What seems odd to me is that if the rundig directive is overriding that of
> the conf file then the files in the db as configured in rundig should have
> been the ones being updated with each run. However, they were not. The db
> files in the db as configured in the conf file were being updated (save the
> pdfs). Once rundig has done it's thing the only directive that matters for
> subsequent searching operations is the one in the conf file. I would run
> rundig and everything would be updated except for the pdf files. This is
> how I know the db files in the conf file directive were the ones being
> affected by the execution of rundig...this is all kind of a moot point
> though since I'm the one that had things mis-configured in the first place...
The rundig we have here defines DBDIR but then uses that definition for the
location of temporary files with the command
and the renaming of the files ending in ".work" which are created with the "-a"
flag to the names without ".work" which are used for searches. The creation of
the database by the htdig command and its next stage of processing by the
htpurge command are not affected by the definition of DBDIR in the rundig
script but rather only by the definition in the htdig.conf file, if there is
one. The default installation creates such a definition in htdig.conf for the
internal variable database_dir which is the same as the initial definition of
DBDIR in the rundig script. If the htdig.conf file does not have a definition,
I would expect htdig and htpurge to use a default based on their own location
but don't know if that's correct.