zsh-workers
 help / color / mirror / code / Atom feed
From: Wayne Davison <wayned@users.sourceforge.net>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: revisiting history-file rewriting
Date: Fri, 18 Mar 2005 09:58:02 -0800	[thread overview]
Message-ID: <20050318175802.GD5500@blorf.net> (raw)
In-Reply-To: <200503181049.j2IAn96p007683@news01.csr.com>

On Fri, Mar 18, 2005 at 10:49:08AM +0000, Peter Stephenson wrote:
> How would this change the result when multiple shells exit at once?
> I'm not entirely clear how the locking affects the fact that multiple
> shells want to rewrite the file in this case.

It doesn't change that behavior except to make it safer -- if zsh is
forcefully killed it might be in the middle of writing out a new copy of
the history file instead of a truncated version of the real history
file.

Note also that for anyone using one of the history-appending options
that I've already eliminated the multi-shell locking contention at
system shutdown time because zsh no longer tries to rewrite the history
file on a kill signal (and doesn't need to touch the history file at all
if it has no history data left to append).

..wayne..


  reply	other threads:[~2005-03-18 17:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 20:40 Wayne Davison
2005-03-17  2:09 ` Geoff Wing
2005-03-17  2:49   ` Wayne Davison
2005-03-18 16:18     ` Andrey Borzenkov
2005-03-18 17:51       ` Wayne Davison
2005-03-18 18:02         ` Wayne Davison
2005-03-17 18:03 ` Bart Schaefer
2005-03-18 18:19   ` Wayne Davison
2005-03-18 21:15     ` Bart Schaefer
2005-03-18 21:47       ` Wayne Davison
2005-03-18 10:49 ` Peter Stephenson
2005-03-18 17:58   ` Wayne Davison [this message]
2005-03-18 18:24     ` Peter Stephenson
2005-03-18 22:53 ` Wayne Davison
2005-03-20  1:57   ` Bart Schaefer
2005-03-21 10:39     ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050318175802.GD5500@blorf.net \
    --to=wayned@users.sourceforge.net \
    --cc=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).