You can recompile with an option to use any file locking method you
want... flock, fcntl, or dot-locking :-)
The bug in bugzilla about this I believe says that we want to find a way
around this. Possibly by making it so that we always dot-lock mailboxes
that are under our control while using the compiled option to lock other
mailboxes on the system if we try to open them.
The other option, I suppose, is to make it a run-time option.
Jeff
On Wed, 2001-09-26 at 10:50, John Graber wrote:
>
> I found that this has been registered as a bug on Bugzilla - but whether it
> is being addressed as a priority is unclear:
>
> I had been happily using Evo for quite some time, when one day I moved my
> home directory to an NFS share. . .
>
> Now, I am unable to receive mail due to locking problems with fcntl(2).
> This has basically made Evo useless to me.
>
> As a sys admin, this seems to me to be a major issue. I have been at
> several sites where all user home directories as located on an NFS share as
> mine are. I would very much like to make Evo our app of choice for personal
> info mgmt. and email but this will prevent that.
>
> What is the priority for addressing this issue? (Please don't tell me I can
> fix it by recompiling with an option! ;)
>
> Thanks for all the hard work!
>
> Prost,
> John
>
>
> _______________________________________________
> evolution maillist - [EMAIL PROTECTED]
> http://lists.ximian.com/mailman/listinfo/evolution
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution
