From xemacs-m  Sun Jul 13 20:28:49 1997
Received: from bittersweet.inetarena.com (karlheg@bittersweet.inetarena.com [206.129.216.38])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id UAA17870
	for <xemacs-beta@xemacs.org>; Sun, 13 Jul 1997 20:28:48 -0500 (CDT)
Received: (from karlheg@localhost)
	by bittersweet.inetarena.com (8.8.5/8.8.5) id SAA04199;
	Sun, 13 Jul 1997 18:28:20 -0700
To: XEmacs Beta <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> <kig67ue8xj7.fsf@jagor.srce.hr>
X-Face: /Q}=yl}1_v7nP)xXo5XjG8+tl@=uVu7o5u6)f]zN?+<hB!K.m9:[|*p34jVN`O;:XZXVSy>/\R>qDt(t8w!-i{(y0"`jFw^uk8inzO9wXabd'CdjUWfC\GHi:6nO*YC89#-qD>Q4r%9!V"<RYJ=7D#$";q=zML5'!=wvXk^$`6FT=5CMofQX)WUKt0p:OKl.mFOXx/D
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: karlheg+xemacs@inetarena.com (Karl M. Hegbloom)
Date: 13 Jul 1997 18:28:16 -0700
In-Reply-To: Hrvoje Niksic's message of "13 Jul 1997 23:14:36 +0200"
Message-ID: <874t9yo21b.fsf@bittersweet.inetarena.com>
Lines: 48
X-Mailer: Gnus v5.4.62/XEmacs 20.3(beta12) - "Helsinki"

>>>>> Hrvoje Niksic writes:

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

    Hrvoje>     ** File locking works with NFS now.

    Hrvoje>     The lock file for FILENAME is now a symbolic link
    Hrvoje> named .#FILENAME, in the same directory as FILENAME.
	[...]
    Hrvoje>     When Emacs or a system crashes, this may leave behind
    Hrvoje> lock files which are stale.  So you may occasionally get
    Hrvoje> warnings about spurious collisions.  When you determine
    Hrvoje> that the collision is spurious, just tell Emacs to go
    Hrvoje> ahead anyway.

 Please have a look at:

<URL:http://inetarena.com/~karlheg/Public/site-lisp/led-funcs.html>

 It's a _small_ set of functions I wrote for editting `smartlist'
`procmail' run control files.  An eval in a Local Variables section
installs an itimer that keeps a lockfile.lock fresh.  I want to extend
it so that after a certain period of time with no activity in the
buffer,[1] the itimer will blonk or pop up a dialog at me to remind me
I have the file open.

 With a per-directory configureable thing similar to `backup-dir.el'
uses, (please see, I will too, I've not read it through.), perhaps
critical central files could be shared this way.  The site admin would
set up a list of locations that need special handling, and set the
amount of time anyone should have a file from there open.

 We could agree that when a lockfile is older than 10 minutes, it can
be considered stale.  Can we assume that clocks will be set properly
on both computers?



Footnotes: 
[1]  How can I do that?

-- 
mailto:karlheg+sig@inetarena.com (Karl M. Hegbloom)
http://www.inetarena.com/~karlheg
Portland, OR  USA
Debian GNU 1.3  Linux 2.1.36 AMD K5 PR-133
You tell me and we'll both know.

