Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Mbox-locking with readonly-filesystem

Discussion topic

Back to topic list

Mbox-locking with readonly-filesystem


Author endremr
Full name Endre Rognerud
Date 2003-03-05 23:44:21 PST
Message Hi!

We have problems with the updating scripts/classes that propagates the
database with emails. The problem is that all our mbox-files is mounted in a
readonly filesystem. When Eyebrowse wants to parse an mbox-file, it tries to
write a lock-file in the same directory, but it's not allowed to write

Is this locking necesarry? The mbox-files will be updated by some other
scripts anyway...

# Class name for file locking implementation (class loaded at run-time)
# Default: org.tigris.eyebrowse​.io.FileLock

I wonder what the best way to solve this is. Should we write our own
FileLocking-class that does nothing, or should we write lock-files to
another directory?

Hope someone can give us an advice :)

To unsubscribe, e-mail: dev-unsubscribe@eyeb​rowse.tigris.org
For additional commands, e-mail: dev-help at eyebrowse dot tigris dot org

« Previous message in topic | 1 of 3 | Next message in topic »


Show all messages in topic

Mbox-locking with readonly-filesystem endremr Endre Rognerud 2003-03-05 23:44:21 PST
     RE: Mbox-locking with readonly-filesystem endremr Endre Rognerud 2003-03-05 23:51:45 PST
         Re: Mbox-locking with readonly-filesystem Daniel Rall <dlr at collab dot net> Daniel Rall <dlr at collab dot net> 2003-03-07 16:56:23 PST
Messages per page: