From: Roland Roberts <rroberts@panix.com>
To: info-gnus-english@gnu.org
Subject: Debugging failed connection attempt.
Date: Tue, 19 Nov 2013 12:35:09 -0500 [thread overview]
Message-ID: <l6g7ge$dqc$1@reader1.panix.com> (raw)
My old ISP has dropped shell support, so I've moved to a new ISP. I've been connecting to news using nntp-open-connection-function nntp-open-via-rlogin-and-telnet and
thought I should only need to change the host information:
(setq gnus-secondary-select-methods
'((nntp "new-alias"
(nntp-open-connection-function nntp-open-via-rlogin-and-telnet)
(nntp-never-echoes-commands t)
(nntp-via-address "new-shell-host")
(nntp-address "new-nntp-server")
(nntp-record-commands t)
(nntp-end-of-line "\n")
(nntp-via-rlogin-command "ssh")
(nntp-via-rlogin-command-switches ("-t" "-e" "none")))))
However, I always get an error when connecting. The " *nttpd*" buffer is empty, there
is no *nntp-log* buffer (with or without a leading space). Additionally, if I run ps
from the shell to see what command is running, it looks fine. I can even cut-and-paste
that command and get dropped to a telnet prompt from which I can open a connection to
"new-nntp-server".
What are my options for debugging this?
roland
next reply other threads:[~2013-11-19 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 17:35 Roland Roberts [this message]
2013-12-25 23:45 ` 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='l6g7ge$dqc$1@reader1.panix.com' \
--to=rroberts@panix.com \
--cc=info-gnus-english@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.
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).