From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Posting to my university's nntp server hangs
Date: Fri, 07 Mar 2014 12:45:15 +0100 [thread overview]
Message-ID: <upzciorq5j1w.fsf@dod.no> (raw)
In-Reply-To: <87k3c6gvkp.fsf@thinkpad-t61.fritz.box>
>>>>> Tassilo Horn <tsdh@gnu.org>:
>> Ok, but do you have similar TLS messages to the bug, in the Messages
>> buffer?
> No, I only get some "Resource temporarily unavailable" messages with
> gnutls-log-level set to 1.
> gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. [13 times]
[snip!]
> gnutls.c: [1] (Emacs) allocating credentials
> gnutls.c: [1] (Emacs) setting the trustfile: /etc/ssl/certs/ca-certificates.crt
> gnutls.c: [1] (Emacs) gnutls callbacks
> gnutls.c: [1] (Emacs) gnutls_init
> gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
> gnutls.c: [1] (Emacs) setting the priority string
> gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. [1216 times]
Ah, probably not the same bug, then...?
next prev parent reply other threads:[~2014-03-07 11:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 9:41 Tassilo Horn
2014-03-05 14:02 ` Lars Ingebrigtsen
2014-03-05 14:12 ` Tassilo Horn
2014-03-05 17:06 ` Lars Ingebrigtsen
2014-03-05 18:16 ` Tassilo Horn
2014-03-05 18:25 ` Lars Ingebrigtsen
2014-03-06 7:37 ` Tassilo Horn
2014-03-06 12:19 ` Tassilo Horn
2014-03-06 12:56 ` Steinar Bang
2014-03-07 8:42 ` Tassilo Horn
2014-03-07 9:30 ` Steinar Bang
2014-03-07 10:19 ` Tassilo Horn
2014-03-07 11:45 ` Steinar Bang [this message]
2014-03-06 13:02 ` Eric S Fraga
2014-03-06 18:15 ` Andreas Schwab
2014-03-07 10:32 ` Eric S Fraga
2014-03-07 15:04 ` Lars Ingebrigtsen
2014-03-07 15:43 ` Tassilo Horn
2014-03-07 15:49 ` Tassilo Horn
2014-03-06 18:14 ` Andreas Schwab
2014-03-07 15:04 ` Lars Ingebrigtsen
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=upzciorq5j1w.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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 NNTP newsgroup(s).