According to Franck Horlaville: > OK, htdig 3.1.6-012702 indexes www.aicha.com without a hitch (13 pages) ...
Great to know! Thanks. > My 3.2 is currently indexing the rest (I've for the moment excluded > aicha.com) so I don't want to stop it ; > > although maybe I can kill it and relaunch it through gdb, what do you > think ? I'm at 14,305 out of roughly 40,000 documents ... Don't kill it on our account! I'd say let it go. However, if you want to test 3.2.0b4 on aicha.com, you can do it even while it's still indexing the other sites. Just create a different .conf file for the test, which sets start_url to http://www.aicha.com/, and sets database_dir to something different so you can run a second copy of the 3.2 htdig from the debugger, using the alternate .conf file, without touching the databases being created by the first run of htdig. Use something like... $ gdb /path/to/3.2.0b4/htdig ... (gdb) run -vvvv -s -i -c alternate.conf ... ... (if it hangs, then hit Ctrl-C, and then...) (gdb) bt ... > by the way when you send a kill statement, it would be great to have > on the stdout something like "kill received, dumping progress log to > /path/file.log" That's a good idea. At least, if you have one or more -v options it ought to do this. It probably should be added to the log dumping section of Retriever::Start(). Should it say this even if no -v options are given, though, or should it run silently in that case? My feeling is the latter, for consistency. Any other opinions? > Are there DB differences between 3.1.6 and 3.2.0 ? In other words, if > this crawl finishes, can I share the databases between the two > versions, like in crawl with 3.1.6 and search with 3.2.0 ? The differences are too substantial between 3.1.x and 3.2.x to allow any conversion of databases from one to the other - especially the word databases. Your only option is to redig when migrating. However, for future 3.2.x development, we'll try to keep the ASCII versions of the databases upward compatible so you can htdump from one 3.2.x version, upgrade to a new one that incorporates extensions to the binary databases, then htload into the new database format. No such path exists for 3.1.x to 3.2.x migration. See also http://www.htdig.org/dev/htdig-3.2/upgrade.html -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 _______________________________________________ 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
