Re: slrn problems
On Thu, 17 May 2001, Joey Hess wrote:
> Dale Scheetz wrote:
> > Since my last upgrade, which now leaves me with slrn 0.9.7.0a-7, I can't
> > get slrn to work at all...
> >
> > sonya@dwarf:~$ slrn -n
> > slrn 0.9.7.0 (Apr 27 2001 00:02:29)
> >
> > Reading startup file /etc/news/slrn.rc.slrn fatal error:
> > Unable to find a fully qualified hostname. You will have to specify a
> > hostname in your .slrnrc file.
>
> What does hostname -f output on your system?
>
> If I do:
>
> joey@silk:~>head -1 /etc/hosts
> 127.0.0.1 silk.kitenet.net
> joey@silk:~>hostname -f
> silk.kitenet.net
>
> Slrn works, but, if I modify my /etc/hosts file:
>
> joey@silk:~>head -1 /etc/hosts
> 127.0.0.1 silk
> joey@silk:~>hostname -f
> silk
> joey@silk:~>slrn
> slrn 0.9.7.0 (May 10 2001 17:23:35)
>
> Reading startup file /etc/news/slrn.rc.
>
> Reading startup file /home/joey/.slrnrc.slrn fatal error:
> Unable to find a fully qualified hostname. You will have to specify a
> hostname in your .slrnrc file.
>
> Of course, removing the line in /etc/hosts entirely works too. (I just
> have it there so hostname -f continues to work if this laptop is
> offline.) The problem is if you have a /etc/hosts line that sets up a
> non-qualified hostname for your computer.
No! The problem seems to be that the hostname dwarf (or dwarf.dwarf.net,
when set fully qualified) resolves to 10.1.1.10, rather than whatever
TalStar provides the PPP connection when I dial in.
>
> I think this check was added in the new version of slrn as just a new
> sanity check. Presumably something breaks if the hostname is not fully
> qualified. (I would guess it wants it for message-id generation..)
Something breaks if you try to specify the structure of the network using
the hostname.
>
> Rather than fooling with the hosts file, you can also follow the
> example set hostname commands in /usr/doc/slrn/examples/slrn.rc.gz
Yea, right ;-(
>
> > If I try to specify the hostname on the command line:
> >
> > sonya@dwarf:~$ slrn -n --nntp -h news.polaris.net
> > slrn 0.9.7.0 (Apr 27 2001 00:02:29)
>
> That's the nnrp server hostname, while slrn is complaining about your
> own.
Well, if it was going to find the news server on my local net it might
have some reason to complain.
dwarf:/home/dwarf# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
max2.talstar.co * 255.255.255.255 UH 0 0 0 ppp0
10.0.0.0 * 255.0.0.0 U 0 0 0 eth0
default max2.talstar.co 0.0.0.0 UG 0 0 0 ppp0
max2.talstar.co is the net containing news.polaris.net, where I get my
news. The local host is dwarf (or dwarf.dwarf.net) and lives on the 10
net.
What do I have to do at this end to get slrn to cooperate?
>
> > Looking at /etc/news, I see the files: server, which contains the hostname
> > of the news server; slrn-help.txt, containing online help; and slrn.rc,
> > which contains some color setup, but no server.
> >
> > The only comments in the slrn manpages state the existance of ~/.slrnrc
> > but give no details about its contents.
>
> Slrn now includes a large manual in manual.txt in the doc directory. I
> reccommend it.
Great! Because of this new feature, the only thing that seems to offer me
any hope of reading news is to revert to an earlier version ;-(
Wishing for a useful upgrade path,
Dwarf
--
_-_-_-_-_- Author of "Dwarf's Guide to Debian GNU/Linux" _-_-_-_-_-_-
_- _-
_- aka Dale Scheetz Phone: 1 (850) 656-9769 _-
_- Flexible Software 11000 McCrackin Road _-
_- e-mail: dwarf@polaris.net Tallahassee, FL 32308 _-
_- _-
_-_-_-_-_- Released under the GNU Free Documentation License _-_-_-_-
available at: http://www.polaris.net/~dwarf/
Reply to: