[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Debugging failed connection attempt.
From: |
Roland Roberts |
Subject: |
Debugging failed connection attempt. |
Date: |
Tue, 19 Nov 2013 12:35:09 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 |
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Debugging failed connection attempt.,
Roland Roberts <=