From: Daniel Colascione <dancol@dancol.org>
To: Andreas Schwab <schwab@linux-m68k.org>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Tassilo Horn <tsdh@gnu.org>,
Michael Albinus <michael.albinus@gmx.de>,
20015@debbugs.gnu.org
Subject: bug#20015: 25.0.50; Slow Emacs startup after recent TRAMP changes
Date: Fri, 06 Mar 2015 14:45:11 -0800 [thread overview]
Message-ID: <54FA2DF7.8020406@dancol.org> (raw)
In-Reply-To: <54FA2B80.3020201@dancol.org>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On 03/06/2015 02:34 PM, Daniel Colascione wrote:
> On 03/06/2015 11:17 AM, Andreas Schwab wrote:
>> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>>
>>>>> % time getent ahosts host.does.not.exist
>>>>> getent ahosts host.does.not.exist 0,00s user 0,00s system 0% cpu 30,013 total
>>>> Which means your system is misconfigured.
>>>
>>> But that's no excuse to impose such a 30s timeout on the user who did
>>> not actually do anything that would explicitly trigger this problem.
>>
>> A working hostname lookup is a fundamental part of the system.
>
> In theory. In practice, lookup is broken all the time, and for good
> reason. We can't always know right away when we don't have connectivity.
> What if I'm on a train and enter a tunnel? Connectivity is interrupted
> for a little while, but not enough to trigger OS network
> reconfiguration. It's inexcusable for Emacs to block for 30 seconds on
> DNS resolution in this case.
It's also unacceptable to start six (by my count) ssh subprocesses,
especially on systems like Cygwin, where process creation is very slow.
At the very least, this work needs to be delayed until someone tries to
use an ssh connection method, and the result should be called.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-06 22:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 6:23 bug#20015: 25.0.50; Slow Emacs startup after recent TRAMP changes Tassilo Horn
2015-03-06 8:29 ` Michael Albinus
2015-03-06 8:53 ` Tassilo Horn
2015-03-06 9:23 ` Michael Albinus
2015-03-06 12:39 ` Tassilo Horn
2015-03-06 13:45 ` Ivan Shmakov
2015-03-06 14:38 ` Andreas Schwab
2015-03-06 14:57 ` Tassilo Horn
2015-03-06 16:43 ` Andreas Schwab
2015-03-06 18:05 ` Stefan Monnier
2015-03-06 19:17 ` Andreas Schwab
2015-03-06 22:34 ` Daniel Colascione
2015-03-06 22:45 ` Daniel Colascione [this message]
2015-03-07 11:35 ` Michael Albinus
2015-03-07 12:17 ` Eli Zaretskii
2015-03-07 20:08 ` Michael Albinus
2015-03-09 4:41 ` Stefan Monnier
2015-03-09 21:11 ` Michael Albinus
2015-03-15 15:14 ` Michael Albinus
2015-03-16 15:24 ` Stefan Monnier
2015-03-16 19:20 ` Michael Albinus
2015-03-16 19:31 ` Tassilo Horn
2015-03-17 9:21 ` Michael Albinus
2015-03-07 2:34 ` Stefan Monnier
2015-03-06 19:51 ` Tassilo Horn
2015-03-06 20:07 ` Andreas Schwab
2015-03-06 20:08 ` Tassilo Horn
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=54FA2DF7.8020406@dancol.org \
--to=dancol@dancol.org \
--cc=20015@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@IRO.UMontreal.CA \
--cc=schwab@linux-m68k.org \
--cc=tsdh@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).