Hi,
On Fri, 2 Apr 1999, Richard Ibbotson wrote:
> I've had a good long look at the Leafnode docs and I can't get
> Leafnode to run. I've definitely got the right nntp server address.
>
> What do I need to do to make/ compile it ? The docs don't quite give
> the full explanation.
Are you using the original source package? I found the INSTALL document
quite easy to follow...
You might want to have a look at the RPM on our ftp-Server, it contains a
README.SuSE under /usr/doc/packages/leafnode, which describes the
necessary steps.
For convenience, I've attached it to this mail. I hope, noone complains
about this...
Bye,
LenZ
--
------------------------------------------------------------------
Lenz Grimmer SuSE GmbH
mailto:[EMAIL PROTECTED] Schanzaeckerstr. 10
http://www.suse.de/~grimmer 90443 Nuernberg, Germany
Installation notes for Package leafnode
---------------------------------------
In order to use leafnode on your system, you have to configure some things
correctly:
o Set the variable NNTPSERVER in /etc/rc.config to point to your local host:
NNTPSERVER="localhost"
Be sure to run SuSEconfig afterwards, this will create the necessary
entry in the file /etc/nntpserver.
o edit /etc/leafnode/config to fit your needs. As a minimum,
you have to insert your preferred News Server in Line 3:
server = <Your server>
This is the name or IP address of your provider's newsfeed. See the
manual page for leafnode(8) for more info about specific configuration
issues.
o to start leafnode when connecting with your newsreader, uncomment the
following line in /etc/inetd.conf:
nntp stream tcp nowait news /usr/sbin/tcpd /usr/sbin/leafnode
This starts leafnode for all connections on the nntp port, subject to
/etc/hosts/allow and /etc/hosts.deny screening. Make sure, that this is
the only line beginning with "nntp"!
o After these changes, force inetd to reread the changed configuration file
To achieve this in SuSE Linux, issue the following command (as root):
rcinetd restart
Alternatively, you may use the following command:
killall -HUP inetd
o Now run fetch. The first run will take some time since fetch reads a
list of all newsgroups from your upstream server. With an 28.8 modem,
it can take as long as 60 minutes (depending on how many newsgroups your
provider offers and how fast your connection is). To see fetch working,
run it with the Option "-vvv".
o Read news using an NNTP client (with $NNTPSERVER or /etc/nntpserver
pointing to your own host). Select the groups you want to read in
the future. You will find them empty except for a default article.
Reading this article is necessary with some newsreaders to select
the groups for further fetching. After this, you should have empty
files in /var/spool/news/interesting.groups/ for every group you want
to read.
o Run fetch again. This run should pick up all the groups you want to read.
You can now read these messages or post new ones with your newsreader,
fetch will deliver your posted messages during the next run.
o If you want to fetch new news every time you go online, you could
run fetch from /etc/ppp/ip-up, for example.
o To clean up old articles, you should run texpire in regular intervals.
An example for /etc/crontab:
0 22 * * * root test -x /usr/sbin/texpire && /usr/sbin/texpire
This would start texpire every night at 10pm. If your machine does not
run 24 hours a day, make sure that you choose a time, when it will be
turned on.
Have a lot of fun,
Your SuSE-Team.
