I have been having lots of timeouts with tin and
I asked about it in eternal-september.support.
A reply said you should try using TLS via port 563.
But tin version 2.6.1 that comes with Slackware 15.0 does
not support this.
So, I took the source of tin tin-2.6.5 from Current and
compiled/installed on my Slackware 15.0 system.
Before compiling you will need to add this argument
'--with-nntps' to the Slackbuild configure step.
I then changed the entry in my File /etc/nntpserver
from "reader443.eternal-september.org" to
"news.eternal-september.org" and the timeouts when away.
To execute you would is argument '-T', something like this:
% rtin -A -T
You can also supply optional argument "-t ###" where ###
is the number of seconds for timeouts. But I believe the
default of 120 will be fine for most people.
This may help out others have the same issue I have
been having.
So far so good,
Regards
John McCue <jmclnx@gmail.com.invalid> wrote:<snip>
I have been having lots of timeouts with tin and
I asked about it in eternal-september.support.
Interesting. I'm using tin-2.6.5 also with eternal-september as
my NNTP server and have had no problems at all. My compile options:
--with-gpg=/usr/local/bin/gpg --with-shell=/bin/bash
--enable-nntp-only --enable-warnings
--with-screen=terminfo --with-domain-name=<mydomain> >--with-nntp-default-server=news.eternal-september.org
--disable-ipv6 --with-coffee --disable-nls
--with-included-gettext --with-Xaw3d --with-x
Compiles successfully, and all I do is pass -A to the binary at
the CLI.
I have been having lots of timeouts with tin and I asked about it in eternal-september.support.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:00:47 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,448 |