From: Conrad Lloyd-Knight <clloydknight@rudolphtech.com>
Subject: Re: slow response on first buffer edit
Date: Fri, 22 Oct 2004 14:04:00 -0400 [thread overview]
Message-ID: <20041022180400.GA2845@kelda> (raw)
Answering my own question here, just in case anyone else runs into
this...
> I have also noticed that this hangup occurs before a symbolic link is
> created, by the name of .#filename, pointing to a non-existant file
> called user@host.name.PID:somelongnumber.
Running emacs with a debugger shows that during this hang time it's
accessing /var/log/wtmp. A look through the code for filelock.c
reveals that the somelongnumber is actually the time of the last
reboot (not sure why...), which emacs is trying to pull from the wtmp
file. Only in my case, the machine in question had a wtmp file over
90MB in size, which caused the delay. Flushing wtmp solved the
problem.
-C.
next reply other threads:[~2004-10-22 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 18:04 Conrad Lloyd-Knight [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-20 18:29 slow response on first buffer edit Conrad Lloyd-Knight
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041022180400.GA2845@kelda \
--to=clloydknight@rudolphtech.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).