On Mar 23, 2007, at 1:54 PM, Sebastien Pahl wrote: > That is exactly what I tried with Ferret but it makes the processes > freeze or raise a Ferret::Store::Lock::LockError.
I'm less than completely familiar with how Ferret handles this, but in KS, you'll get a lock error after the timeout is exceeded and it stops retrying. A freeze sounds wrong. I suspect the only way to make this work is to catch the LockError and retry. Creating a queue for writers trying to access an NFS index, so that each new process starts immediately after an old process releases a lock... that would be great, but I don't know how you'd pull it off with lock files. Creating shared read locks was hard enough! Marvin Humphrey Rectangular Research http://www.rectangular.com/ _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
