From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: 9fans@9fans.net
Subject: [9fans] nupas improper error output
Date: Sun, 16 May 2010 03:45:48 -0100 [thread overview]
Message-ID: <AANLkTin00PeUM6_RB6jipdI2fhucfgdXGrE5IlEnm6RH@mail.gmail.com> (raw)
The following tells the story:
term% /n/sources/plan9/386/bin/upas/fs -f /imaps/imap.gmail.com
/n/sources/plan9/386/bin/upas/fs: opening /imaps/imap.gmail.com:
imap.gmail.com/imaps:server certificate XXX not
term% upas/fs -f /imaps/imap.gmail.com
upas/fs: opening /imaps/imap.gmail.com: imap.gmail.com/imaps:fd out of
range or not open
(cert replaced with "XXX")
So there's some part of the error reporting
in nupas that hides the real problem, which
is with the certificate having changed.
Best,
ak
next reply other threads:[~2010-05-16 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 4:45 Akshat Kumar [this message]
2010-05-16 5:29 ` erik quanstrom
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=AANLkTin00PeUM6_RB6jipdI2fhucfgdXGrE5IlEnm6RH@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/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).