Re: Noffle with tin

On 01-Jul-2004 Balas Mark wrote:
>> If you're using inetd, you need to replace the 'nntp' line there with
>> nntp stream tcp nowait news /usr/sbin/tcpd /usr/local/bin/noffle -r
>>
>> (assuming your noffle executable is in /usr/local/bin). If it's xinetd you
>> use,
>> edit packages/redhat/noffle-xinetd and change 'disable = yes' to 'disable =
>> no', and copy it to /etc/xinetd.d and remove any file there that runs
>> leafnode.
> 
> I did it (which noffle said that the executable is in /usr/bin/noffle);
> now tin connects to localhost, than gives the error message
> 
>    Connection to news server has timed out. Reconnect? (Y/n) Y

Let's start by making sure that Noffle is installed and will work as a server.

First, I think you said you'd done a 'noffle --query groups' and a 'noffle
--fetch' to populate the news base with groups and some articles.

Now try a quick server session run from the command line. Here's one I just
did. The lines I typed to the server are indicated by '>'.

  jim@fluffy:~$ noffle -r
  200 NNTP server NOFFLE 1.1.4
> list active uk.comp.os.*
  215 Groups
  uk.comp.os.win95 2317 2317 y
  uk.comp.os.linux 56726 56374 y
  uk.comp.os.win2000 4655 4655 y
  .
> quit
  205 Goodbye
  jim@fluffy:~$

You may not get the same group list.

Assuming that all works, the remaining problem is sorting out inetd or xinetd.
The goal is to be able to do the same as above but via a network connection,
like this:

  jim@fluffy:~$ telnet localhost nntp
  Trying 127.0.0.1...
  Connected to localhost.
  Escape character is '^]'.
  200 NNTP server NOFFLE 1.1.4
  list active uk.comp.os.*
  215 Groups
  uk.comp.os.win95 2317 2317 y
  uk.comp.os.linux 56726 56374 y
  uk.comp.os.win2000 4655 4655 y
  .
  quit
  205 Goodbye
  Connection closed by foreign host.
  jim@fluffy:~$

This, by the way, is what inetd or xinetd do - they handle the network port, and
start a program to service the connection. That program thinks it is just
talking to standard input and output.

If you can do the above telnet session successfully, then Noffle is correctly
installed as a server, and the problem is with the tin configuration.

Now, your system will be using inetd or xinetd, but not both. Most modern Linux
distros use xinetd, but not all - Debian, for example, uses inetd by default.
I'm guessing from what you said that you have xinetd. This is trickier for me
to help with, 'cos I'm on Debian. Can you mail the contents of the noffle file
you put in /etc/xinetd.d and we'll check for the problem.

> I guess I am overlooking something trivial again (because of my nearly
> complete lack of experience). I do appreciate your patience.

No problem - I've battled (x)inetd in the past. You're not the only one to have
problems. I do know that this is the difficult stage; don't worry - we will get
there.

-- 
Jim Hague - [email protected]          Never trust a computer you can't lift.


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com