According to Dan Langille: > On 20 Nov 2002 at 14:39, Jonathan Schlackl wrote: > > Hi Dan, > > > > So does that mean I need to run a merge like this? > > htmerge -c configfile > > htmerge -c configfile2 > > htmerge -a -v -c configfile -m configfile2 > > Let's not miss any steps in the example: > rundig -vvv -a -c configfile2 > htdig2.out > htmerge -c configfile2 > htmerge -a -v -c configfile -m configfile2 > > rundig -vvv -a -c configfile3 > htdig3.out > htmerge -c configfile3 > htmerge -a -v -c configfile -m configfile3
Except that if you are indeed running "rundig", and not "htdig", to generate each index to begin with, then rundig already runs htmerge after running htdig (assuming you're running version 3.1.x). If you're running version 3.2.x, then you should run htpurge after htdig, which the rundig script in 3.2 will also do. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This sf.net email is sponsored by: Battle your brains against the best in the Thawte Crypto Challenge. Be the first to crack the code - register now: http://www.gothawte.com/rd521.html _______________________________________________ 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
