my current (the default, I made no changes to it ) start_url is set to-- start_url: http://localhost/
looking at the attributes page for start_url it states that I can add more than one url, but it does not show how to do this. Would it be-- start_url: http://localhost/ , http://localhost/~user/ http://localhost/home/user/public_html/ ???? Are they seperate lines each starting with start_url, combined as one line with a space between or a common between with or without spaces?
The URLs specified should be those you would type into a browser's address field to view the sites in question; htdig will make requests and see responses in a manner nearly identical to that of an ordinary web browser. As for separators, the URLs should be separated by white space. You may either added all of the URLs on a single line or break them up across multiple lines. If you do the latter, you need to end all of the lines, other than the last one, with a '\', which serves as a line continuation character. When using a line continuation character, you need to be careful that there is no space (or other characters) after the continuation character.
If you have a large number of URLs to include, you can also enter the URLs in a separate file and simply specify that file in the start_url attribute. If you do this the filename must be enclosed in backticks (e.g. `somefile`). Some of this information is stated in the comment accompanying the start_url attribute in the default configuration file.
I've tried several ways and each time get the DB2 error about no string defined.
If this problem is recurring regardless of how your attributes are set, you might want to delete any existing ht://Dig databases to ensure that you are not struggling with corrupt database file.
Also, would I have to adjust my limit_urls_to attribute as well?
This depends on how you specify the start_url. By default limit_urls_to is set to the same thing as start_url. If you are using URLs of form http://someserver/somepath/ limit_urls_to generally does what you want. If you are explicitly providing start_url with specific files (e.g. http://someserver/somepath/file.html), then you will probably need to tailor limit_urls_to to your specific needs.
And lastly, if I have created documents with .htm extension rather than .html do I need to specify that somewhere?
Generally not for ht://Dig. If you are using .htm for your index files (e.g. index.htm), you might need to configure your web server to recognize them as such. For the most part if a URL works the way you want with a web browser, it will also work the way you want with htdig.
Jim
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ 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
