From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: It's almost 2016 and when (single-threaded) Emacs hangs, you gotta be smashing your keyboard!
Date: Thu, 19 Nov 2015 17:36:34 -0700 [thread overview]
Message-ID: <20151119173002889401548@bob.proulx.com> (raw)
In-Reply-To: <87egfly9s7.fsf@kuiper.lan.informatimago.com>
Pascal J. Bourguignon wrote:
> Alexander Shukaev writes:
> > In this particular case, I'm talking about Linux and directories
> > mounted from network.
>
> Yeah, right.
>
> This freezes unix, not emacs. You might prefer to access remote files
> using tramp.
I want to emphasize this. If you are accessing files over NFS and for
whatever reason the NFS server goes away this causes the NFS client in
the local kernel to wait. The "freeze" you are seeing is a freeze in
the NFS client and not Emacs. The problem is in the kernel not emacs.
NFS client is implemented in the kernel. When it locks up there is
absolutely nothing an application can do to unlock the kernel. This
has been a plague on NFS forever. Problems with the NFS client are
the one thing that may require the workstation to be rebooted.
Because if it were an application in userspace one could kill and
restart it. But because NFS is implemented in the kernel the only way
to kill and restart the kernel is to reboot.
The only way to win is not to play. Which is what Pascal suggests
with using emacs tramp to avoid nfs client and instead use ssh or
other to access those files. Because tramp operates entirely in
userspace it can't lock up the same way.
Bob
P.S. Emacs has been rock solid for me for the last decade. I can't
remember the last time I experienced an emacs crash. Bugs in
behavior? Sure. But no crashes.
next prev parent reply other threads:[~2015-11-20 0:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 20:29 It's almost 2016 and when (single-threaded) Emacs hangs, you gotta be smashing your keyboard! Alexander Shukaev
2015-11-19 20:36 ` John Wiegley
2015-11-19 20:57 ` Alexander Shukaev
2015-11-19 21:15 ` Eli Zaretskii
2015-11-19 20:46 ` Eli Zaretskii
2015-11-19 20:55 ` Alexander Shukaev
2015-11-19 21:09 ` Eli Zaretskii
[not found] ` <mailman.264.1447966512.31583.help-gnu-emacs@gnu.org>
2015-11-19 21:11 ` Pascal J. Bourguignon
2015-11-20 0:36 ` Bob Proulx [this message]
2015-11-20 10:49 ` Rasmus
2015-11-22 21:43 ` Xavier Maillard
2015-11-22 22:24 ` Stefan Monnier
2015-11-23 5:11 ` Xavier Maillard
2015-11-23 3:34 ` Eli Zaretskii
2015-11-23 5:13 ` Xavier Maillard
2015-11-23 13:52 ` John Wiegley
2015-11-23 1:19 ` MBR
[not found] ` <mailman.285.1447979800.31583.help-gnu-emacs@gnu.org>
2015-11-20 7:53 ` Loris Bennett
2015-11-20 9:42 ` Michael Albinus
2015-11-19 21:25 ` Dmitry Gutov
2015-11-19 21:43 ` Random832
2015-11-19 22:18 ` Dmitry Gutov
2015-11-20 7:54 ` Eli Zaretskii
[not found] ` <mailman.262.1447966007.31583.help-gnu-emacs@gnu.org>
2015-11-23 0:12 ` Jason Rumney
[not found] <mailman.258.1447964949.31583.help-gnu-emacs@gnu.org>
2015-11-19 21:09 ` Pascal J. Bourguignon
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=20151119173002889401548@bob.proulx.com \
--to=bob@proulx.com \
--cc=help-gnu-emacs@gnu.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.
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).