* Debugging failed connection attempt.
@ 2013-11-19 17:35 Roland Roberts
2013-12-25 23:45 ` Lars Ingebrigtsen
0 siblings, 1 reply; 2+ messages in thread
From: Roland Roberts @ 2013-11-19 17:35 UTC (permalink / raw)
To: info-gnus-english
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-12-25 23:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-19 17:35 Debugging failed connection attempt Roland Roberts
2013-12-25 23:45 ` Lars Ingebrigtsen
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).