pfBlockerNG and Config History
-
All,
Noticed that even when there appears to be no change, pfBlockerNG is causing another config file to be written. Looks like one of the "description" fields is updated, regardless of change. Took a 12 hour span where there were no administrative changes to the system and the configuration history shows the following for every hour:
(system): pfBlockerNG: saving DNSBL changes
Would expect that only when a configuration change is made - that a new history element would be created vs. when feeds are updated, that those changes are captured in the logs. As a result, the default of "30" for configuration history doesn't cover much 'time' (even without any administrative changes). Is this the expected behavior? While increasing the configuration history isn't an issue, it seems rather wasteful to have a litany of [effectively] useless entries in the configuration history (chewing up disk space) vs. legitimate historical changes to enable look-back.
Thanks!
-
@justme2 said in pfBlockerNG and Config History:
that a new history element would be created vs. when feeds are updated
Exact.
I also discovered that the DNSBL feeds I use aren't actually really updated (new content) so, I switched to :
== weekly. And not every hour, which is, IMHO, pure mdnss.
ok, ok, Maybe I'm missing a host name or two during a day or so.
But it's a fact : my config history becomes useful now :
And its also nicer to the DNSBL hoster that I don't hit there servers to often ^^
-
@Gertjan Right. Although interval of update shouldn't matter, it just seems 'odd' that a description field appears to be updated in config.xml with every run and yet the "feeds" themselves are outside of the config.xml - thus there shouldn't be another config backup. At least I'm not the only person who's experiencing this.
Cheers'
