innd dies

[Jan Ploski]

On Mon, Mar 20, 2000 at 12:03:21AM +0900, Katsuhiro Kondou wrote:
> } Again, I would greatly appreciate your help. Isn't there
> } a complete listing of error/log messages produced by INN?
> 
> I suspect innd died unexpectedly, and core might be left.

I did not find 'core' anywhere in my INN subtree, and this sudden death
after a minute or two is happening again and again. I suspect that it is
caused by one of my outgoing feeds (I have two) -- when I commented it out
in 'newsfeeds', innd was running okay for over 24 hours (and accepting news
from an incoming feed from the same site). However, I really need to be able
to send my articles to there, as it is our interface to the world (the other
one is internal to our site). Any idea what I could do to get rid of this
problem?

One possible approach that comes to my mind is to use "nntpsend" instead
of "innfeed" and see if it works. Can you tell me what are the relative
(dis)advantages of both methods of feeding news? The FAQ only elaborates
on how to set up an "nntpsend" feed. Maybe I am doing something wrong.
On the other hand, the feed to the internal site, which is exactly the
same with respect to newsgroups and method as the other one, does not seem
to cause any trouble.

BTW, I understand that the outgoing feeds should be named after what
appears in the "Path" header of articles received from the respective site.
Right? Now I also have a file named 'incoming.conf' where 'peer' definitions
appear. I was unable to find the man page for this file, and I am wondering
whether the peer names in there should/are allowed to match the peer names
from innfeed.conf.

Thanks in advance for your kind explanations,

-JPL