Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

INN FAQ Part 7/9: Problems with INN already running
Section - (7.4) How come my host name comes out twice in the Path line?

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Houses ]


Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.3) Suddenly my active and history files are owned by root!
Next Document: (7.5) Expire had problems and won't run again after fixing the problem
See reader questions & answers on this topic! - Help others by sharing your knowledge
The INN server puts its name in the Path line of every article that it
receives.  Obviously, it has to do this.  The default configuration has
inews put the local host in the Path header.  If nobody posts on the
server and you use fully-qualified domain names on your workstations,
then everything works the right way.  (If `hostname` doesn't give an
FQDN on your machine, you can work-around this by setting the "domain"
value in inn.conf; remember that innd never re-reads inn.conf.  You
must "ctlinnd shutdown x" and then re-start the server).  Many people
don't want the client machines to put their name in the Path header.
To do this, set INEWS_PATH to DONT.  Finally, let me say that it is
probably a mistake to have a "pathhost" line on any machine other than
your server if you set INEWS_PATH to DO.  If you doubt this, please
trace the article flow for yourself.  If you are curious about the
effect of INEWS_PATH, read the nroff source -- not the formatted
output -- of doc/inews.1

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.3) Suddenly my active and history files are owned by root!
Next Document: (7.5) Expire had problems and won't run again after fixing the problem

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)





Last Update November 21 2011 @ 01:00 PM