For our example innd has it's configuration files in
/opt/news/etc. All of its files should be owned and readable
by the news user.
The ones that need changing are listed below:
ME:*,!junk,!to,!test::
demon::Tf,Wnm:demon
crosspost:*:Tc,Ap,WR:/opt/news/bin/crosspost
overview!:*:Tc,WO,S30000:/opt/news/bin/overchan
If you have local newsgroups that you don't want to, or can't propogate to Demon then you can add them on the demon newsfeeds line. Thus:
demon:!local.*:Tf,Wnm:demonwould prevent articles posted in the local hierarchy being
propogated.
peer ME {
hostname: localhost
}
peer sample {
hostname: sample.demon.co.uk
}
where you obviously replace sample with your demon hostname.
*:: -no- : -no- :!*
stdin:Read Post:::*
localhost:Read Post:::*
Other hosts can be added in the same format as localhost. You
can also specify usernames, passwords and restrict access to certain groups by
using the last three fields. For instance:
*.local.net:Read Post:user:pass:!alt.sex.*allows access to any computer in the domain local.net which logs in
with username user and password pass to any newsgroup
except those in the alt.sex hierarchy.
This controls who articles are sent to. With the newsfeeds entry
above the following will upload all posted articles to Demon's news server
demon:news.demon.co.uk::
To actually send the articles you'll need to invoke
nntpsend, more on that later.
A lot of this can be ignored and left as the default. The ones you should set are as follows
server: sample.demon.co.uk
pathhost: sample.demon.co.uk
fromhost: sample.demon.co.uk
doinnwatch: false
innflags: -L
You may want to put something witty in the organisation: line as
well