That is exactly what I tried with Ferret but it makes the processes 
freeze or raise a Ferret::Store::Lock::LockError.

Marvin Humphrey wrote:
> On Mar 23, 2007, at 10:46 AM, Matt Schnitz wrote:
> > 
> What is possible is to manage access to an index on a shared volume
> so that an active write process causes all other attempts to open a
> write process to fail, including those from other machines.  The key
> is to put the write.lock file in the index directory, rather than in
> the temp directory -- since the temp directory is per-machine, no
> other machine knows about another machine's lock files and write
> processes may stomp each other.
> 

--
Sebastien Pahl - Rift Technologies
[EMAIL PROTECTED]

-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk

Reply via email to