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 WAA15690 for ; Wed, 10 Apr 1996 22:25:28 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id IAA05960; Wed, 10 Apr 1996 08:13:17 -0400 (EDT) Resent-Date: Wed, 10 Apr 1996 08:13:17 -0400 (EDT) From: Zefram Message-Id: <19260.199604101212@stone.dcs.warwick.ac.uk> Subject: Re: History file locking? To: seniorr@teleport.com (Russell Senior) Date: Wed, 10 Apr 1996 13:12:15 +0100 (BST) Cc: zsh-workers@math.gatech.edu In-Reply-To: <199604101031.DAA04027@linda.teleport.com> from "Russell Senior" at Apr 10, 96 03:31:58 am X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]7332.54 X-US-Congress: Moronic fuckers MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Xcc713.0._S1.SNwQn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/904 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >In order to keep Zsh from trashing its history file, I have >implemented the following local patch. Perhaps this can be worked >into the source tree? This patch uses the fcntl() function to lock >the entire contents of the history file during read and write >operations, using the corresponding blocking read and write locks. I think it's a good idea, but the patch can't be included as-is. There needs to be a configure test to check if this type of locking is available, and perhaps to try using flock() as a backup mechanism, if available. -zefram