it is hard to see whole picture since you are just sending changing
snippets of configuration - send the whole entirety...
I bet that the reason for current issue is that
you defined actionstart in [Definition] config/action.d/iptables.conf
whenever you defined in post_start_commands in [Init] --- how can it see
its value in Definition?? define it in new section [DEFAULT] of the same
file then... and you might need to define it to smth nonempty - I am not
sure what freaks ConfigParser out exactly
once again - this is not a fail2ban issue but rather logic behind usage
of python interpolations in config files
On Wed, 15 Nov 2006, martin f krafft wrote:
> also sprach Yaroslav Halchenko <[EMAIL PROTECTED]> [2006.11.15.1512 +0100]:
> > I believe that you mixed up interpolations (done but pythons config module)
> > and
> > substitutions done by fail2ban
> > actionstart = iptables -N fail2ban-<name>
> > iptables -I <fwchain> -m state --state NEW -p <protocol>
> > --dport <port> -j fail2ban-<name>
> > <post_start_commands>
> > I don't think that it is fail2ban intent to substitute
> > post_start_commands here -- try using interpolations %(...)s
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
