[Evolution-hackers] Making file-locking configurable at runtime? (UG#4795)



Hi,

We have a somewhat complex intranet consisting of several XDMCP/NFS
servers and we're running applications with NFS mounted home folders
(probably other folders too).

NFS servers are running in vserver context and are using somewhat
modified kernels (some security and vserver patches added) so I've been
told that we're not able to get rpc.statd work properly. Thus, neither
fcntl() nor flock() works for us.

For that reason, I have re-packaged evolution with file-locking disabled
and dot-locking enabled. While we're at it, we have been wondering if it
could be possible to make it configurable at runtime.

What I think is, to convert compile time things a lookup to GConf and do
the preferred way of locking. If I come up with a patch implementing
this, would that ever get committed?

Thanks,
-- 
.O.
..O   Enver ALTIN                   |   http://skyblue.gen.tr/
OOO   Software developer @ Parkyeri | http://www.parkyeri.com/

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]