On Thu, 12 Jul 2001, Karl Pielorz wrote:
> But, I then thought if I run the dig/merge (using the '-a' for
> alternate workfiles option) against just a single server, I'd end up
> with the information in the database for the server I just ran dig
> against, being updated, or added to the current database... [after
> renaming the .work files back to their original names].
Let me get this straight. You ran a dig on 1,000 servers, ran htmerge and
have these files under the normal filenames. Then you run htdig/htmerge
with the -a option--which ONLY considers filenames with .work
appended. Then you moved the .work files over the original databases?
Whatever filenames are specified in the config file or by -a are the only
files that the programs examine. At the moment, there isn't any real
locking, which is why you don't want to write the the "live" databases.
What you really want to do is to set up another config file with a
different database_dir or something along those lines. Then do the dig,
run htmerge, and then run htmerge -m <one-server.conf> -c <main.conf>
<http://www.htdig.org/htmerge.html>
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
