From: Dominik Vogt <dominik.vogt@gmx.de>
To: Zsh Users <zsh-users@zsh.org>
Subject: Bug: Losing .zsh_history
Date: Wed, 5 Oct 2022 20:55:26 +0100 [thread overview]
Message-ID: <Yz3hLjGCw/bccjFY@localhost> (raw)
Due to some hardware problem with the display adapter my box
sometimes fails to show anything on the screen but just emits some
error beeps while it boots. Since I cannot log in and stop the
machine without the screen, I can only switch off the power.
It has now happened twice that in the wake of the hard switch-off,
~/.zsh_history got completely erased, replaced with all null
characters, but keeping its size (or at least nor being truncated
to zero size). This is on Linux 4.x (5.x not being compatible
with the very old hardware) using ext 4 without journal, running
Devuan 4. Losing history is a real big pain because for me
because it's one huge database of past commands and syntax (2
million lines).
(However, I'm not sure why ~/.zsh_history is modified at all
because it should be touched only when logging in?)
I wonder if this situation could be prevented by changing the code
that writes the history file at exit. Is truncating the file to
zero size part of the procedure? When I need to write a file in a
safe manner, the procedure normally looks like this:
* Create file.new
* Rename file to file.old
* Rename file.new to file
(* Possibly sync filesystem)
* Erase file.old
--
$ zsh --version
zsh 5.8 (x86_64-debian-linux-gnu)
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
next reply other threads:[~2022-10-05 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:55 Dominik Vogt [this message]
2022-10-05 20:01 ` Eric Cook
2022-10-05 20:20 ` Dominik Vogt
2022-10-05 21:05 ` Wesley
2022-10-05 21:24 ` Dominik Vogt
2022-10-05 22:31 ` Bart Schaefer
2022-10-05 23:03 ` Dominik Vogt
2022-10-06 4:34 ` Bart Schaefer
2022-10-06 9:40 ` Peter Stephenson
2022-10-06 10:52 ` Dominik Vogt
2022-10-06 10:30 ` Dominik Vogt
2022-10-05 20:26 ` Dominik Vogt
2022-10-05 22:16 ` Bart Schaefer
2022-10-05 22:32 ` Dominik Vogt
2022-10-06 10:31 ` Dominik Vogt
2022-10-07 11:45 ` Mikael Magnusson
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=Yz3hLjGCw/bccjFY@localhost \
--to=dominik.vogt@gmx.de \
--cc=zsh-users@zsh.org \
/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).