> Thank you for the prompt response.
Sure, but if you could keep the list CC'ed in the message, your replies won't end up in the bottom of my INBOX. Thanks. > 1. The major reason that we like to use htdig v3.2 is the external protocol > option for us to index https and other non-http protocols. Correct me if I > am wrong, I do not recall v.3.1.6 has external protocol option yet. Before the 3.2 development, the ht://Dig code was tied directly to HTTP. It is not feasible to "add" external protocol code to 3.1.x, no. > 2. What if the htdig return value 139 is the runtime error such as > segmentation fault? Unfortunately, the failed rundig was executed from > crontab and did not leave a trace of core dump file. And what is more > interesting is that the rundig for last night is successfully completed with > return value 0. I agree to use -vvv for the rundig to generate more > debugging info if the incident happens again. A segmentation fault would be very strange and we take them pretty seriously. Even a segmentation fault in an external parser or protocol handler should not take down htdig directly. So if you can reproduce this with some additonal debugging information, we'd greatly appreciate it and try to patch the bug ASAP. Thanks, -Geoff -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ 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
