OK. Thanks for the additional info.
On Fri, 29 Dec 2000, Douglas Kline wrote:
I've been running some tests and my results don't seem consistent with your
description.
I think a better way of saying this is "my description wasn't very good."
Let me put it this way:
-a = "add
On Fri, 29 Dec 2000, Douglas Kline wrote:
I've been running some tests and my results don't seem consistent with your
description.
I think a better way of saying this is "my description wasn't very good."
Let me put it this way:
-a = "add .work to the database names before doing anything"
-i
Geoff,
I've been running some tests and my results don't seem consistent with your
description. Is it possible that when you use both the -a and the -i flags to
htdig, it creates the new files using the ".work" extension and leaves the
existing files in place for searches to read and differs
On Tue, 26 Dec 2000, Douglas Kline wrote:
The description of the "-a" flag adds, "When used without the "-i"
flag for an update dig, htdig will use any existing .work files for
the databases to update." Where would these "existing .work files"
come from? Wouldn't such files be removed at
OK. Thanks for the info.
The best way to describe this is to say that the -a flag just means that
htdig (and company) will add the .work extension to the database filenames
before opening them.
Douglas Kline
[EMAIL PROTECTED]
To
According to the documentation, the "-i" flag to htdig which is in the rundig
file in the distribution causes htdig to create a database anew after erasing
the existing database and the "-a" flag which is not in the rundig file in the
distribution is used to create a new database while leaving
