all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matt Armstrong <matt@rfc20.org>
To: Gunnar Horrigmo <gnunar@stoffe-pro.net>, emacs-devel@gnu.org
Subject: Re: locked history file
Date: Tue, 16 Feb 2021 10:10:45 -0800	[thread overview]
Message-ID: <m2v9arzxwa.fsf@matts-mbp-2016.lan> (raw)
In-Reply-To: <iv4sg5wfg30.fsf@hot-rats.uio.no>

Gunnar Horrigmo <gnunar@stoffe-pro.net> writes:

> Has something changed recently regardomg how emacs handles the history
> file? I'm seeing this quite often now, when running multiple emacsen:
>
> Error running timer ‘savehist-autosave’: (file-locked "/home/gunnar/.config/emacs/emacs.d/history" "gunnar@titanium (pid 1039)")
>
> .. and while it's perfectly understandable, I've been running multiple
> emacsen for many, many years, and this feels new.
>
> This is on 27.1.91, btw.
>
> I apologise if this is too noobish for emacs-devel. I appreciate a
> pointer if I should've asked elsewhere.

Hi Gunnar,

I have been digging into the Emacs file locking code recently.  I don't
think much has changed with core mechanics locking mechancis or savehist
itself in recent Emacs versions.

How big is your history file?  Perhaps it is enormous, causing the IO to
take an unusualy long time.

How is your hard disk?  If it is seeing intermitten write slowness at
other times?  Could you be doing IO intensive tasks when these problems
occur?

When you run your multiple Emacs instances, do you launch them all at
the same time?  For example, at login?  If so, then the history save
timers would all happen at similar times, which would increase the
chance of a write lock conflict.

Those are all "shot in dark" guesses.

Feel free to file an Emacs bug on this.



  parent reply	other threads:[~2021-02-16 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 10:43 locked history file Gunnar Horrigmo
2021-02-16 15:52 ` Eli Zaretskii
2021-02-16 23:57   ` Gunnar Horrigmo
2021-02-16 18:10 ` Matt Armstrong [this message]
2021-02-17  0:01   ` Gunnar Horrigmo

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=m2v9arzxwa.fsf@matts-mbp-2016.lan \
    --to=matt@rfc20.org \
    --cc=emacs-devel@gnu.org \
    --cc=gnunar@stoffe-pro.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.