From: Simon Josefsson <jas@extundo.com>
Subject: Re: nntp problems with hibernating and waking up in a new network
Date: Thu, 15 Dec 2005 11:48:09 +0100 [thread overview]
Message-ID: <iluoe3ibpqu.fsf@latte.josefsson.org> (raw)
In-Reply-To: <871x0f5t1t.fsf@dod.no> (Steinar Bang's message of "Wed, 14 Dec 2005 21:21:02 +0100")
Steinar Bang <sb@dod.no> writes:
>>>>>> Simon Josefsson <jas@extundo.com>:
>
>> Try adding `(message "foo")' etc, or use edebug, or remove the
>> condition-case to see where it blows up.
>
> Hm... I've found a working workaround for the problem (wrap all nntp
> connections in telnet). Do you still need/want me to debug this?
No.
> I haven't verified that a cached DNS server is the problem. But the
> delay for each NNTP server, fits gethostbyname() time out.
>
> And if this _is_ the problem, then the problem is outside of Gnus, and
> even outside of Emacs. It is a libc problem, and as such probably
> best just worked around...
Yes, probably.
next prev parent reply other threads:[~2005-12-15 10:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 10:02 Steinar Bang
2005-12-12 15:56 ` Simon Josefsson
2005-12-12 17:29 ` Steinar Bang
2005-12-13 16:33 ` Simon Josefsson
2005-12-13 18:51 ` Adrian Aichner
2005-12-13 19:19 ` Steinar Bang
2005-12-14 14:15 ` Simon Josefsson
2005-12-14 20:21 ` Steinar Bang
2005-12-15 10:48 ` Simon Josefsson [this message]
2005-12-13 18:57 ` Steinar Bang
2005-12-12 16:53 ` Jesper Harder
2005-12-12 17:22 ` Steinar Bang
2005-12-12 22:19 ` Bjørn Mork
2005-12-13 12:34 ` Steinar Bang
2005-12-13 14:00 ` Steinar Bang
2005-12-13 16:33 ` Steinar Bang
2005-12-13 19:24 ` Steinar Bang
2006-01-18 11:35 ` gmane spam reporting problems moving between networks (Was: nntp problems with hibernating and waking up in a new network) Steinar Bang
2006-01-19 10:13 ` gmane spam reporting problems moving between networks Simon Josefsson
2006-08-02 19:38 ` gmane spam reporting problems moving between networks (Was: nntp problems with hibernating and waking up in a new network) Steinar Bang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=iluoe3ibpqu.fsf@latte.josefsson.org \
--to=jas@extundo.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 NNTP newsgroup(s).