Thanks for the tips.. I'm using version 3.1.6. I have cleared the db directory. While I did start out using rundig, I have been using htdig too while trying to figure this out. I went into the config file and made sure there was newline at the end.
Still getting no output whatsoever from htdig -i -vvv. Very perplexing. I talked to my associate, all he did was add a bunch of pdfs. Mind you, I had it indexing pdfs without any problem before. And even if there were a problem with the pdfs, I should be getting debug messages. Thanks for your suggestions. If you have any more I'd love to hear them. Daniel Crandall Unix/Network Administrator Texas Department of Housing and Community Affairs. 512-305-8574 [EMAIL PROTECTED] -----Original Message----- From: Gilles Detillieux [mailto:[EMAIL PROTECTED] Sent: Friday, November 21, 2003 11:01 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [htdig] -vvv produces no output at all According to Daniel Crandall: > I've got a rather perplexing problem. > I had htdig configured and working fine, indexing our test site including > .pdfs and .docs. > My associate added a bunch of .pdfs and made a bunch of changes, so I went > to re-index the site. > > Tried rundig -avvv, and got nothing. Literaly. No debug output, it created rundig is a shell script and doesn't do well with combined options, especially the -a and -s which it tries to intercept. You may want to try rundig -a -vvv. > a db.docdb.work that was 2k in size. > I have since tried htdig -i -vvv, as well. Nothing. In both cases it just > sits there. It gobbles up cpu like it's trying to do something, but nothing > happens. > > Now regardless of any problems created by his changing the site, why would > -vvv not give any output whatsoever? I would think that even if for some > reason every link were getting excluded for some reason, I would be getting > debug messages to that effect. In addition to the tips Jim provided (clearing out the database directory, checking the config file or reverting to the original), I'd also suggest making sure you have a final newline character on the last line of the file. With the config parser in 3.2 betas, we've noticed a number of problems if this final newline is left out. (You didn't mention which version you're running.) If all else fails, try adding more -v's, and if you still don't get any usable output, let us know which version you're running, and on which platform (hardware, OS distribution and version). You may also want to try reinstalling from source if it's an old installation. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ 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
