Your message dated Tue, 06 May 2008 15:32:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#479703: fixed in fail2ban 0.8.2-3
has caused the Debian Bug report #479703,
regarding fail2ban: PID file does not contain PID of running process
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
479703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479703
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fail2ban
Version: 0.8.2-2
Severity: important

Even after a fresh restart of fail2ban, the PID file at
/var/run/fail2ban/fail2ban.pid contains a PID that differs from that of
the running fail2ban process.  This hinders monitoring.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.9-023stab044.16-enterprise (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages fail2ban depends on:
ii  lsb-base                      3.2-11     Linux Standard Base 3.2 init scrip
ii  python                        2.5.2-1    An interactive high-level object-o
ii  python-central                0.6.6      register and build utility for Pyt

Versions of packages fail2ban recommends:
ii  iptables                      1.4.0-3    administration tools for packet fi
ii  whois                         4.7.26     the GNU whois client

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.8.2-3

We believe that the bug you reported is fixed in the latest version of
fail2ban, which is due to be installed in the Debian FTP archive:

fail2ban_0.8.2-3.diff.gz
  to pool/main/f/fail2ban/fail2ban_0.8.2-3.diff.gz
fail2ban_0.8.2-3.dsc
  to pool/main/f/fail2ban/fail2ban_0.8.2-3.dsc
fail2ban_0.8.2-3_all.deb
  to pool/main/f/fail2ban/fail2ban_0.8.2-3_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yaroslav Halchenko <[EMAIL PROTECTED]> (supplier of updated fail2ban package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Tue, 06 May 2008 10:49:34 -0400
Source: fail2ban
Binary: fail2ban
Architecture: source all
Version: 0.8.2-3
Distribution: unstable
Urgency: low
Maintainer: Yaroslav Halchenko <[EMAIL PROTECTED]>
Changed-By: Yaroslav Halchenko <[EMAIL PROTECTED]>
Description: 
 fail2ban   - bans IPs that cause multiple authentication errors
Closes: 479703
Changes: 
 fail2ban (0.8.2-3) unstable; urgency=low
 .
   * Changes propagated from upstream trunk (future 0.8.3):
     - Fixed "fail2ban-client get <jail> logpath". Bug #1916986.
     - Changed some log level.
     - Added "Day/Month/Year Hour:Minute:Second" date template. Thanks to
       Dennis Winter.
     - Fixed PID file while started in daemon mode. Thanks to Christian
       Jobic who submitted a similar patch (closes: #479703)
     - Added gssftpd filter. Thanks to Kevin Zembower.
     - Process failtickets as long as failmanager is not empty.
   * Assure that /var/run/fail2ban exists upon start (LP: #222804, #223706)
Checksums-Sha1: 
 9611be64aeb2f0047295f6010cd5bbf34de33432 1177 fail2ban_0.8.2-3.dsc
 3c8ea8dfec7bbf03b56c6959b327e9ec219c7695 25503 fail2ban_0.8.2-3.diff.gz
 eb2e2680c3a2c69fca082f10588ca5e66bf3005a 82890 fail2ban_0.8.2-3_all.deb
Checksums-Sha256: 
 6772c43072d6bf08417b55ce9e9cbd8007152282be826df528591b3ee5505566 1177 
fail2ban_0.8.2-3.dsc
 d3e8d8cd8d4db12d5c301ac686cc8c967cf3671ecfce29c2479966d061fc5043 25503 
fail2ban_0.8.2-3.diff.gz
 6cbd88920ccfa2f05689d8bec3d4c31bf5c13fb0438d0ff3731a07dae02a0e30 82890 
fail2ban_0.8.2-3_all.deb
Files: 
 a17232828396642a98757a4ba8c6c42e 1177 net optional fail2ban_0.8.2-3.dsc
 3ed43f120314c9d283c8f0b25127f045 25503 net optional fail2ban_0.8.2-3.diff.gz
 ea5492962c12f3c5afef7ba57b0484cd 82890 net optional fail2ban_0.8.2-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIIHUXjRFFY3XAJMgRAtzRAKCb1+C1qyJ/WJM+ys/V2f81rb/CNQCfc3zw
YSAav0yJPZwBV6rRfgR4jao=
=ezwG
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to