According to Robert Isaac: > Thank you, this is now working OK. However, after putting the authorization > parameters into htdig.conf, when I ran rundig it did not automatically run > htmerge, htnotify and htfuzzy, as it did on all occasions before. I had to > run them each manually. Is there a connection here or is there another > problem? Thanks again for your help.
I can't imagine any connection between the authorization attribute in htdig.conf and rundig not running htmerge, etc., unless you were also giving the rundig command some command-line options (such as the -u option) which work only with htdig and not with htmerge, htnotify and htfuzzy. The other thing you should make sure of is that you haven't made any changes to rundig which might prevent it from running all needed commands, or that you don't have different, incompatible versions of rundig lying around. E.g., if you installed a 3.2 beta release of htdig at some point, its rundig script is not compatible with the 3.1.6 release. Note that some systems, like Red Hat Linux, may install htdig 3.2 by default, so be sure you're running the right rundig script and/or remove any remnants of ht://Dig releases you don't want. -- 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: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ 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
