From: Glenn Morris <rgm@gnu.org>
To: Michael Olson <mwolson@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Emacs Development Discussions <emacs-devel@gnu.org>
Subject: Re: Fixing dired hangs when NFS mount goes AWOL
Date: Wed, 05 Oct 2011 18:14:20 -0400 [thread overview]
Message-ID: <0jty7nnl1f.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAN4ruPhxsowYrxqiyuUU2zZ45xNgz1zv-_1t+75h02v0kC1wsg@mail.gmail.com> (Michael Olson's message of "Wed, 5 Oct 2011 14:59:24 -0700")
>>> Would you consider adding "-l" to the list of default arguments for
>>> `directory-free-space-args'? This will fix an issue where attempting
>>> to open dired buffers with ls-lisp enabled hangs due to an AWOL NFS
>>> mount.
Could you explain what the issue actually is?
Normally even trying to ls a directory containing eg a link to a missing
NFS directory hangs.
Are you saying that doing dired on a local directory that contains a
link to a missing NFS mount works, but hangs in calling df to calculate
the 'total used xxx available yyy' part?
What does ls-lisp have to do with it?
I can see how adding -l might help with a plain `df' call, but how can
it help `df DIR' if DIR is local?
next prev parent reply other threads:[~2011-10-05 22:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 18:50 Fixing dired hangs when NFS mount goes AWOL Michael Olson
2011-10-05 21:27 ` Chong Yidong
2011-10-05 21:59 ` Michael Olson
2011-10-05 22:14 ` Glenn Morris [this message]
2011-10-05 22:34 ` Michael Olson
2011-10-05 22:55 ` Glenn Morris
2011-10-05 23:14 ` Glenn Morris
2011-10-05 23:27 ` Michael Olson
2011-10-05 23:31 ` Michael Olson
2011-10-06 12:25 ` Stefan Monnier
2011-10-06 13:18 ` Michael Albinus
2011-10-06 13:25 ` Eli Zaretskii
2011-10-06 15:22 ` Stefan Monnier
2011-10-06 17:58 ` Michael Albinus
2011-10-06 21:18 ` Stefan Monnier
2011-10-07 11:43 ` Michael Albinus
2011-10-07 13:41 ` Stefan Monnier
2011-10-06 18:45 ` Michael Olson
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=0jty7nnl1f.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=mwolson@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.
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).