On Mon, 2003-11-17 at 17:49, Gilles Detillieux wrote:
> Well, right you are.  And, in fact, this is true, but what the
> documentation doesn't say is that the single "-" to get it to read
> from stdin must be after all the other options.  Otherwise, the "-"
> causes htdig to stop scanning the argument list for option arguments,
> so it wouldn't see your -c option (even if -m wasn't swallowing it!).
> So, I'm guessing here that htdig is using the default htdig.conf file,
> instead of the one you want, and so it end up updating a different
> database.  Is this right?  In any case, you need to follow the -m
> with a filename, even if the final "-" overrides it.
> 
> The behaviour we actually want to shoot for is what 3.1.6 does, which
> I think is much more consistent and logical (and better documented).
> See http://www.htdig.org/htdig.html to see what it should be.
> 
> In the meantime, You should probably do something like this:
> 
> echo 'http://newfind.mcgill.ca/indexes/ads/?AdsID=1026232' |
>         ./htdig -s -v -m foo -c /www/htdig/install/conf/ads.conf -
> 
> The "foo" will be ignored.

 Ahh, thank you for clarifying this and for your workaround. The above
line works, and I can re-index my URL! I spent so much time trying all
sorts things to get this to work. Now I can move forward on what I was
doing. Thanks again!

Cheers,

Chris

-- 
Christopher Murtagh
Enterprise Systems Administrator
ISR / Web Communications Group 
McGill University
Montreal, Quebec
Canada

Tel.: (514) 398-3122
Fax:  (514) 398-2017


-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
ht://Dig Developer mailing list:
[EMAIL PROTECTED]
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev

Reply via email to