On Tue, 20 Apr 2004, Steve Yeazel wrote: > I've got a directory of .pdfs that are being indexed properly. I recently > had to make minor changes to each of the files. After making the changes I > figured I would just need to re-run rundig with no options to get the new > file data in to the database. This wasn't the case and I had to delete the > files in /db and then run rundig. Is this the common procedure or am I > missing something? Thanks.
Something is wrong with your setup. Or at least changed from the default. Out of the box, rundig will call htdig with a '-i' which results in any existing databases being deleted before new databases are built. Have you modified rundig? Are you sure that you were running rundig as a user with sufficient permission to delete the old databases and write new ones? Did you try running with a -v in order to see what was actually happening under the covers? Did you notice whether there was a db.log file in the database directory before you deleted everything? If so, that could have also contributed to the problem; this file is left behind when htdig is killed and can cause some unexpected behavior the next time that htdig is started (i.e. htdig tries to use the log to resume where it left off when killed). Jim ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ 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
