innfeed.conf vs incoming.conf

[Bill Davidsen]

Miquel van Smoorenburg wrote:
> In article <cgl8sf$9h0$1 at gatekeeper.tmr.com>,
> Bill Davidsen  <davidsen at tmr.com> wrote:
> 
>>Miquel van Smoorenburg wrote:
>>
>>
>>>I understand that in inn 2.5 or 2.6 the newsfeeds, incoming.conf and
>>>innfeed.conf files are going to be merged ... FINALLY :)
>>
>>Let's hope not! Each of these files controls a single characteristic of 
>>the system and is not related to the others in a deterministic fashion. 
>>That is, changes in incoming.conf don't cause or require changes in 
>>newsfeeds or innfeed.conf, changes in newsfeeds don't require changes in 
>>incoming.conf and may or may not cause changes in innfeed.conf, etc.
>>
>>While it does make for more files to edit, each has a single purpose, 
>>and is therefore much easier to understand (ie. explain to newbies). 
> 
> 
> Really. My experience has been the exact opposite. Also, it's
> really hard to keep the 3 files in sync.

They don't have to be in sync. Changes in incoming.conf have no 
interaction with newsfeeds or innfeed.conf, newsfeeds are generated at 
some sites without ever running innfeed at all, changes to innfeed.conf 
for peer config need no changes in newsfeeds, etc.

The only one-time interaction is that you typically want an entry in 
newsfeeds if you have one in innfeed.conf, and even that's not cast in 
stone, you can feed innfeed from other sources.

-- 
    -bill davidsen (davidsen at tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me