The problem I get with RUNDIG (as also noted on the above homepage) is:
/home/mywebsite/www/cgi-bin/search/bin/rundig: line 36: 13294 Killed $BINDIR/htdig -i $opts $stats $alt
This would seem to imply that something external to ht://Dig is killing your htdig process before it completes. Are you perhaps running htdig from a web hosting account that places a limit on the resources a process is allowed to use (e.g. memory, clock time, cpu time)? That would by my first guess. If you are performing a large dig and sucking down a lot of resources, it might also be that an admin somewhere is manually killing the process.
You might try running rundig with some -v's to get more verbose output, but most likely that will be of little help since the problem seems to be due to something outside of the ht://Dig package. If this is some sort of hosting account, you should probably start by confirming that runs of long-lived executables are supported; some hosting accounts place an upper limit on how long things can run and automatically kill them if the limit is exceeded.
htmerge: Total word count: 3724 htmerge: Document database has no URLs. Check your config file and try running htdig again.
This is just the fallout from the script moving on to htmerge after htdig fails to run to completion.
I am on a shared Redhat Linux server, and use the default C (I think it should be GCC+?)
ht://Dig uses both C and C++ compilers. A reasonably standard Red Hat install with GCC compiler system should be fine.
Jim
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
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
