Re: [Evolution] fcntl, NFS, and Evo 0.8
- From: JP Rosevear <jpr ximian com>
- To: David Sims <david simscomputing com>
- Cc: bds jhb ucs co za, evolution helixcode com
- Subject: Re: [Evolution] fcntl, NFS, and Evo 0.8
- Date: 14 Jan 2001 18:44:57 -0500
On 12 Jan 2001 13:34:01 -0700, David Sims wrote:
On 12 Jan 2001 08:53:11 +0200, Berend De Schouwer wrote:
On Thu, 11 Jan 2001 23:38:13 David Sims wrote:
| Hi, I'm running Evo 0.8 on a Debian 2.2 (potato) box. Evo 0.8 is
| installed via Helix Update.
|
| My home directory is NFS-mounted and I'm getting the dreaded fcntl
| error. This prevents me from using Evo 0.8. The NFS client is this
| Debian 2.2 box. The NFS server is Red Hat 6.1.
Upgrade RH6.1's NFS server (just download 6.2's), or mount the NFS
drive with the mount option '-nolock'. NOTE: -nolock does exactly
what it says.
Fixed!
For the record, this is what I had to do. On the Debian 2.2 client
machine, I mounted my home directory using the "-nolock" option. But
that alone didn't fix it. Still got fcntl errors. I later found out I
also had to turn on "nfslock" on the Red Hat 6.1 server machine like so:
chkconfig nfs on
chkconfig nfslock on
/etc/rc.d/init.d/nfslock start
/etc/rc.d/init.d/nfs start
Bottom line: I had to turn on nfslock on the Red Hat 6.1 server machine.
I didn't have to install any new RH 6.2 RPMs, thankfully.
Thanks Berend for your help! (now I don't even mind the way Evo 0.8
duplicates every incoming message to twice the message's original size
and content :-)
For future reference, the fcntl and flock file locks can be disabled at
compile if necessary.
-JP
--
--
=======================================================================
JP Rosevear jpr ximian com
Ximian Inc. http://www.ximian.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]