From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3) with ESMTP id XAA16332 for ; Wed, 10 Apr 1996 23:02:31 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id IAA06759; Wed, 10 Apr 1996 08:50:39 -0400 (EDT) Resent-Date: Wed, 10 Apr 1996 08:50:39 -0400 (EDT) From: Zefram Message-Id: <20845.199604101250@stone.dcs.warwick.ac.uk> Subject: Re: History file locking? To: hzoli@cs.elte.hu (Zoltan Hidvegi) Date: Wed, 10 Apr 1996 13:50:13 +0100 (BST) Cc: A.Main@dcs.warwick.ac.uk, zsh-workers@math.gatech.edu In-Reply-To: <199604101241.OAA16421@turan.elte.hu> from "Zoltan Hidvegi" at Apr 10, 96 02:41:39 pm X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]7332.67 X-US-Congress: Moronic fuckers MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"a32W92.0.Xf1.UwwQn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/906 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >Also things get quite complicated when the history file is on an NFS volume. >Probaly some dot-locking method similar to the one used by sendmail & co >should be used. I wouldn't bother -- it's only a history file. lockf() (and fcntl()) locking work over NFS anyway; it's only flock() that doesn't. O_EXCL isn't reliable over NFS, which makes .lock locking rather pointless. -zefram