From: Alexander Shukaev <emacs@alexander.shukaev.name>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Emacs-devel
<emacs-devel-bounces+emacs=alexander.shukaev.name@gnu.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs Hangs on Filesystem Operations on Stale NFS
Date: Mon, 11 Jun 2018 14:11:45 +0200 [thread overview]
Message-ID: <7466e2d177e79983436af2425ceb5b54@alexander.shukaev.name> (raw)
In-Reply-To: <CAM-tV--AtCxSVS18VLnGNKao8xb4KV3GWFx3nA+=C92To8mn2g@mail.gmail.com>
On 2018-06-11 13:59, Noam Postavsky wrote:
> On 11 June 2018 at 06:27, Alexander Shukaev
> <emacs@alexander.shukaev.name> wrote:
>
>> Well, enough rant. I think I have a proposal how to fix the issue,
>> even
>> given the blocking nature of Emacs. How about introducing a variable
>> `file-access-timeout' defaulting to `nil', which would reflect a
>> configurable timeout for all access operations (such as
>> `file-readable-p')?
>> This would be achieved via `SIGALARM' in the C code, which would
>> protect
>> every such operation. For example,
>
> Does it work? According to some messages on the previous thread you
> referenced [1], NFS hangs happen in the kernel so a signal would not
> help.
>
> [1]:
> https://lists.gnu.org/archive/html/help-gnu-emacs/2015-11/msg00266.html
Go ahead and try:
import os
import signal
import subprocess
class Alarm(Exception):
pass
def alarm_handler(signum, frame):
raise Alarm
path = '/mnt/<nfs>'
signal.signal(signal.SIGALRM, alarm_handler)
signal.alarm(3)
try:
proc = subprocess.call('stat ' + path,
shell=True,
stderr=subprocess.PIPE,
stdout=subprocess.PIPE)
stdoutdata, stderrdata = proc.communicate()
signal.alarm(0)
except Alarm:
print "Timed out after 3 seconds..."
next prev parent reply other threads:[~2018-06-11 12:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 10:27 Emacs Hangs on Filesystem Operations on Stale NFS Alexander Shukaev
2018-06-11 11:01 ` Andreas Schwab
2018-06-11 11:05 ` Alexander Shukaev
2018-06-11 11:50 ` Andreas Schwab
2018-06-11 12:03 ` Alexander Shukaev
2018-06-11 11:55 ` Alexander Shukaev
2018-06-11 11:59 ` Noam Postavsky
2018-06-11 12:11 ` Alexander Shukaev [this message]
2018-06-11 12:20 ` Noam Postavsky
2018-06-11 12:22 ` Alexander Shukaev
2018-06-11 12:34 ` Noam Postavsky
2018-06-11 12:41 ` Alexander Shukaev
2018-06-11 12:40 ` Andreas Schwab
2018-06-11 12:46 ` Alexander Shukaev
2018-06-11 15:51 ` Eli Zaretskii
2018-06-13 15:40 ` Paul Eggert
2018-06-12 17:26 ` Davis Herring
2018-06-12 18:26 ` Perry E. Metzger
2018-06-11 15:04 ` Stefan Monnier
2018-06-11 16:46 ` Mike Kupfer
2018-06-11 17:08 ` Stefan Monnier
2018-06-13 10:45 ` Alexander Shukaev
2018-06-13 12:35 ` Yuri Khan
2018-06-13 14:23 ` Stefan Monnier
2018-06-13 15:30 ` Yuri Khan
2018-06-13 18:09 ` Michael Albinus
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=7466e2d177e79983436af2425ceb5b54@alexander.shukaev.name \
--to=emacs@alexander.shukaev.name \
--cc=emacs-devel-bounces+emacs=alexander.shukaev.name@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).