[Eisfair_dev] brute_force_blocking (BFB) 0.6.7 testing released

[Rolf Bensch]

Hallo Olaf,

nach Update von einer deutlich älteren Version erhalte ich stündlich:

Job /etc/init.d/brute_force_blocking restart cron 2&>/dev/null 
terminated (exit status: 1) (mailing output)

wohl im direkten Zusammenhang mit:

BFB_UNBLOCK_TIME  =  1 * * * *
BFB_RESTART_ON_UNBLOCK =  yes

BFB scheint aber zu laufen:

# ps -A | grep brute
28266 pts/0    00:00:00 brute_force_blo

Manuelles Ausführen in der Konsole mit:

BFB_LOGLEVEL =  debug
BFB_USE_RAMDISK =  yes
BFB_RUN_IN_DEBUG_MODE =  yes

ergibt:

Sep 28 19:30:33 n36l fcrontab[16985]: installing file /tmp/fcr-s7lbiz 
for user root
Sep 28 19:30:33 n36l fcron[11214]: updating configuration from 
/var/spool/fcron
Sep 28 19:30:33 n36l fcron[11214]: adding new file root
Sep 28 19:30:33 n36l fcrontab[16989]: installing file /tmp/fcr-EbKdNJ 
for user wwwrun
Sep 28 19:30:33 n36l fcron[11214]: SIGTERM signal received
Sep 28 19:30:33 n36l fcron[11214]: Exiting with code 0
Sep 28 19:30:35 n36l fcron[16999]: fcron[16999] 3.1.2 started
Sep 28 19:30:35 n36l fcron[16999]: @reboot jobs will only be run at 
computer's startup.
Sep 28 19:30:35 n36l fcron[16999]: updating configuration from 
/var/spool/fcron
Sep 28 19:30:36 n36l fcron[16999]: adding file wwwrun
Sep 28 19:30:36 n36l fcron[16999]: adding file root
Sep 28 19:30:36 n36l fcron[16999]: adding new file wwwrun
Sep 28 19:30:36 n36l fcron[16999]: adding new file root

Ich sehe jetzt kein konkretes Problem das die Fehler-Mail verursacht.

Grüße

Rolf