Does passing the -a switch to htpurge cause it to work on .work databases if they already exist or does it overwrite existing .work dbs with it's own? The documentation does not make it clear:

http://www.htdig.org/dev/htdig-3.2/htpurge.html

I'm asking because the customized rundig.sh script I'm using runs htpurge -a after htdig -a but before moving the .work files to the live databases. In other words with an existing set of databases, I do (generally):

htdig -a
htpurge -a
copy .work to live dbs

when perhaps I should be doing:

htdig -a
copy .work to live dbs
htpurge -a
copy .work to live dbs

The documentation made me wonder if htpurge isn't actually operating on the databases that were created on the last run rather than on the current run (since, in the first scenario, the current dbs still have .work on them).

Any help?

Ted Stresen-Reuter



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
ht://Dig general mailing list: <[EMAIL PROTECTED]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general

Reply via email to