Le 09-10-2016, Gérald Niel nous expliquait dans
news.admin.peering
(<
slrnnvk6gj.27r.gerald.niel+spam@news.gegeweb.org>) :
But I don't peer with any of them but I solved some similar problems
by forcing stream mode on some peers or disabling stream mode for
others.
How to do that?
Just streaming: false for the peer in innfeed.conf?
According to the innfeed.conf man page, yes:
"GLOBAL PEER DEFAULTS
All the key:value pairs mentioned in this section can be
specified at global scope. *They may also be specified inside a
group or peer definition*. Note that when peers are added dynamically
(i.e. when innfeed receives an article for an unspecified peer), it
will add the peer site using the parameters specified at
global scope."
I'm not sure it will help you but you can give it a try.
I think, it's just incoming.conf to reload.
You may also specify streaming mode in incoming.conf.
I do that in a crontab every night and use exclusively fqdn for peers.
Then, nothing to do if the IP for a fqdn change.
I always used fqdn and I think most newsmasters do but INN have a DNS
cache of some sort that is managed by dns-expire and dns-retry
parameters in innfeed.conf. AFAIR default values are pretty high and can
be annoying with peers using dynamic IP addresses (2 peers of mine use
dynamic IP addresses).
--
Et moi je reste assis les poumons dans la sciure
A filer mes temps morts à la mélancolie.
Soleil, soleil,
N'est ce pas merveilleux de se sentir piégé ?
H.F. Thiéfaine- 713705 Cherche Futur
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)