According to Christopher Murtagh: > In some of my tests, I came across this error: > > WordDB: CDB___memp_cmpr_read: unable to uncompress page at pgno = 402 > WordDB: PANIC: Input/output error > DB_RUNRECOVERY: Fatal error, run database recovery > > and I realize that this might be due to the method in which I'm doing my > indexes and purges. I'm using database triggers to index or purge new > pages, and they could concievably happen concurrently. Does htdig and > htpurge use file locking to prevent problems, or should I be sure to > control this and make sure that concurrent indexes can't happen?
There are currently no file locking mechanisms in htdig, so you need to control this yourself to avoid concurrent updates to the databases. -- 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 Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
