zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Steve Reid <sreid@sea-to-sky.net>
Cc: zsh users <zsh-users@sunsite.auc.dk>
Subject: Re: confused by history
Date: Mon, 15 May 2000 06:21:57 +0000	[thread overview]
Message-ID: <1000515062157.ZM14966@candle.brasslantern.com> (raw)
In-Reply-To: <20000513124926.A416@grok.localnet>

On May 13, 12:49pm, Steve Reid wrote:
} Subject: Re: confused by history
}
} I've found that when I boot my computer in the morning and start my X
} session with a few xterms, occasionally all of my zsh'es have an empty
} history. I'm don't know what's causing it but presumably it has
} something to do with the zsh'es all getting killed at shutdown.
} 
} I also get files with names like ".history.1234" congregating

The 1234 in those file names is a process ID.  Those are the lock files
zsh 3.1.6 (or thereabouts) creates to prevent multiple processes writing
to the history at the same time.  They get unlinked when writing the
history is finished.

If you're seeing those files pile up, then you're killing off your shells
with some kind of signal before they have a chance to finish shutting
down.  It sounds like you may actually be running "shutdown" after your
X server exits and then powering off the computer?  If so, you probably
want to put in a bit of a delay so that the processes have more time to
finish up before they get killed.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~2000-05-15  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-12 18:58 Eric Smith
2000-05-13 19:49 ` Steve Reid
2000-05-15  6:21   ` Bart Schaefer [this message]
2000-05-14  2:37 ` Bart Schaefer

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=1000515062157.ZM14966@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=sreid@sea-to-sky.net \
    --cc=zsh-users@sunsite.auc.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).