Package: fail2ban
Version: 0.7.5-2etch1
Severity: minor

It's not possible to set the poll interval. 
On my light server, fail2ban is continuously running, generating 80% of
CPU wakeup according to powertop.

I have 7 process to monitor ssh and exim, as following:

 6068 python2.4 /usr/bin/fail2ban-server -b -s /var/run/fail2ban.sock
 6069  \_ python2.4 /usr/bin/fail2ban-server -b -s /var/run/fail2ban.sock
 6070      \_ python2.4 /usr/bin/fail2ban-server -b -s /var/run/fail2ban.sock
 6114      \_ python2.4 /usr/bin/fail2ban-server -b -s /var/run/fail2ban.sock
 6115      \_ python2.4 /usr/bin/fail2ban-server -b -s /var/run/fail2ban.sock
 6120      \_ python2.4 /usr/bin/fail2ban-server -b -s /var/run/fail2ban.sock
 6121      \_ python2.4 /usr/bin/fail2ban-server -b -s /var/run/fail2ban.sock

6068 is running continously (strace):
        gettimeofday({1210801673, 533845}, NULL) = 0
        select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)
with a timeout of 50000µs, or 0,05 seconds, it's fired 20 times per seconds

6069 is better, only every other second
        getppid()                               = 6068
        poll([{fd=4, events=POLLIN}], 1, 2000)  = 0
timeout is 2000ms, or 2 seconds; it's better, but what is it doing?

6070 is once a second
        poll([{fd=3, events=POLLIN}], 1, 1000)  = 0
timeout is 1000ms or 1 sec

6114, 6115, 6120, 6121 are also once a second
        stat64("/var/log/exim/mainlog", {st_mode=S_IFREG|0640, st_size=442383, 
...}) = 0
        select(0, NULL, NULL, NULL, {1, 0})     = 0 (Timeout)
timeout is 1 second.

So I have 20 + 0.5 + 1 + 4x1 = 25.5 CPU wake-up every second to monitor 2
files; I think it's a bit too high and I expect it to be configurable to
about 1 wakeup for 5 seconds or 15 seconds.


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable'), (100, 'oldstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.25.3.skc3
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages fail2ban depends on:
ii  iptables                1.3.6.0debian1-5 administration tools for packet fi
ii  lsb-base                3.1-23.2etch1    Linux Standard Base 3.1 init scrip
ii  python                  2.4.4-2          An interactive high-level object-o
ii  python-central          0.5.12           register and build utility for Pyt
ii  python2.4               2.4.4-3+etch1    An interactive high-level object-o

fail2ban recommends no packages.

-- no debconf information



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to