According to Pub Litics: > Hi, thanks for the great input. Good news (I think). As instructed, > I went into the htdig.conf file to check for hidden characters. And, > it was loaded with M-underline (carriage returns). I stripped all of > those out and re-indexed and, behold, when I ran a search I did not come > up with any forum-related, database entries for the sub-directories I > was trying to exclude. Wow, so, I will do more testing but, for now, > it seems that the problem is solved. Guess those hidden characters > somehow gummed up the works. So glad to have the tip. I, also, > had placed exclude_urls all on the same row.
If you're talking about cat -v output, it should show carriage returns as ^M, not M-_. See my previous reply to Greg Fenton in this thread. > As for ver. 3.1.6 and why I am running 3.1.5, I recall a great deal of > difficulty in installation, when we tried the newest version, initially, > and being instructed to use the older version 3.1.5, which has worked > fine and seems to be working fine, now. Should we go with "if it it > is not broken, don't fix it?" [Translation: I am pretty technophobic]. > Or, do you strongly recommend that we go with 3.1.6? Whatever you say, > we'll do. We are on a shared server, however, and do not have root > access, so that had been a problem in the past and could possibly be > an obstacle now. Just let us know what you recommend. As Geoff said, we recommend 3.1.6 for security and stability. What was the difficulty in installing 3.1.6 before, or were you trying to install one of the 3.2 beta releases? 3.1.6 was released back in February of this year, and is the most recent stable release. Older 3.2.0 beta releases do pose a number of problems. If you encounter problems installing 3.1.6, we'd like to know what the specific error messages are that you get. > By the way, in further reply to your inquiry, we have not changed > rundig in any way. Not sure what you mean by line-character as > line-terminator. Line FEED character as line terminator. See my previous reply to Greg Fenton in this thread for more details. > We are not using mac, but a PC (plain-text-editor). When performing the > last edit, we removed all of the M-underline characters, so, at present, > there are no hidden characters in htdig.conf file, at all. Is that the > way it is supposed to be? Does that answer your question, adequately? Well, I'm satisfied that you removed whatever characters were causing problems, as evidenced by the fact that it's now working for you. It just raises the troubling question about whether htdig is choking on CR characters in the file. My reading of the code says it shouldn't, so either I'm reading it wrong, or the offending characters in your file were something other than CRs. I wouldn't mind getting to the bottom of this question. What tool/program/command did you use to remove these characters? > Finally, I did not check the file date-stamp, because, as I mentioned, > I think it is now working, by excluding the proper sub-directories. > I, also, am not posting the htdig.conf file, for the same reason. > But, I shall, of course, if the problem crops up, once again. OK? Sounds reasonable to me. -- 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:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ 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
