From xemacs-m  Sun Jul 13 16:14:42 1997
Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id QAA17090
	for <xemacs-beta@xemacs.org>; Sun, 13 Jul 1997 16:14:39 -0500 (CDT)
Received: (from hniksic@localhost)
	by jagor.srce.hr (8.8.6/8.8.6) id XAA12767;
	Sun, 13 Jul 1997 23:14:36 +0200 (MET DST)
To: XEmacs Developers <xemacs-beta@xemacs.org>
Subject: Re: filelock.c
References: <199707101802.OAA07461@anthem.CNRI.Reston.Va.US> 	<199707101937.PAA05003@verve.canada.sun.com> <199707102003.QAA07519@anthem.CNRI.Reston.Va.US> <m2afjq7j6s.fsf@altair.xemacs.org>
X-Attribution: Hrv
X-Face: Mie8:rOV<\c/~z{s.X4A{!?vY7{drJ([U]0O=W/<W*SMo/Mv:58:*_y~ki>xDi&N7XG
        KV^$k0m3Oe/)'e%3=$PCR&3ITUXH,cK>]bci&<qQ>Ff%x_>1`T(+M2Gg/fgndU%k*ft
        [(7._6e0n-V%|%'[c|q:;}td$#INd+;?!-V=c8Pqf}3J
From: Hrvoje Niksic <hniksic@srce.hr>
Date: 13 Jul 1997 23:14:36 +0200
In-Reply-To: Steven L Baur's message of "13 Jul 1997 14:09:47 -0700"
Message-ID: <kig67ue8xj7.fsf@jagor.srce.hr>
Lines: 37
X-Mailer: Gnus v5.4.59/XEmacs 20.3(beta12) - "Helsinki"

Steven L Baur <steve@xemacs.org> writes:

> It defaults to disabling file locking.  I suppose we should take a
> poll to vote on what the default should be.  I'd like to see it
> enabled by default.

Me too.  I don't think I like disabling file locking by default,
because it suddenly cuts one of the quite important features of
XEmacs.

How about handling it differently?  Here is what FSF 20.0 does:

    ** File locking works with NFS now.

    The lock file for FILENAME is now a symbolic link named .#FILENAME,
    in the same directory as FILENAME.

    This means that collision detection between two different machines now
    works reasonably well; it also means that no file server or directory
    can become a bottleneck.

    The new method does have drawbacks.  It means that collision detection
    does not operate when you edit a file in a directory where you cannot
    create new files.  Collision detection also doesn't operate when the
    file server does not support symbolic links.  But these conditions are
    rare, and the ability to have collision detection while using NFS is
    so useful that the change is worth while.

    When Emacs or a system crashes, this may leave behind lock files which
    are stale.  So you may occasionally get warnings about spurious
    collisions.  When you determine that the collision is spurious, just
    tell Emacs to go ahead anyway.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
ED WILL NOT CORRUPT YOUR PRECIOUS BODILY FLUIDS!!

