Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Re: [Throughput-l] new fail2ban config -- Re: Anacron job 'cron.daily' on ps1.ochep.ou.edu

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Re: [Throughput-l] new fail2ban config -- Re: Anacron job 'cron.daily' on ps1.ochep.ou.edu


Chronological Thread 
  • From: Shawn McKee <>
  • To: Horst Severini <>, "<>" <>
  • Cc:
  • Subject: [perfsonar-user] Re: [Throughput-l] new fail2ban config -- Re: Anacron job 'cron.daily' on ps1.ochep.ou.edu
  • Date: Fri, 17 Feb 2017 10:54:19 -0500
Hi Horst,

The quick answer is I don't know.  I find that I don't have a jail.conf.rpmnew.  My jail.conf has 333 non-comment, non-empty lines:
[root@psum01 fail2ban]# grep -v "^#" jail.conf | grep -v "^$"  | wc
    333     908   10443

My guess would be there is new stuff being tracked if you use the new .conf file.   How different is the current one from the jail.conf.rpmnew one?

 I am adding the perfSONAR users list.

Shawn

On Fri, Feb 17, 2017 at 9:10 AM, Horst Severini <> wrote:
Hi all,

I noticed that the new fail2ban jail.conf.rpmnew looks very different
from the current one. Is there some manual interaction required
in order to keep thing operating properly, or can we just ignore this
and fail2ban will still work fine with the old config file?

Thanks,

        Horst

Anacron <> wrote:

> /etc/cron.daily/0yum.cron:
>
> warning: /etc/fail2ban/jail.conf created as /etc/fail2ban/jail.conf.rpmnew
_______________________________________________
Throughput-l mailing list

https://lists.bnl.gov/mailman/listinfo/throughput-l


Archive powered by MHonArc 2.6.19.

Top of Page