Conrad Schilbe's bits of Tue, 15 Oct 2002 translated to: >My first post to this mailing list... if it should go somewhere else, >let me know.
For this type of question, the htdig-general lists would be more appropriate than the developer list. >Currently this is how I see it happening. I create multiple instances >of rundig that index the individual sites and create database files for >each. I then create a copy of these and merge them into one common >index. Sounds like a reasonable approach. ht://Dig is certainly capable of handling this type of setup. >Is there components of the database that should not be duplicated for >each site? Is there an easier way to achieve my goals? Maybe a way to >have one db but specify the site within the args? Have you read http://www.htdig.org/FAQ.html#q4.20 ? In particular the parts about restrict and exclude? Also see http://www.htdig.org/attrs.html#exclude http://www.htdig.org/attrs.html#restrict These attributes provide a means for filtering search results in a manner that might be useful for what you are trying to do. Jim ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
