Your message dated Thu, 2 Mar 2006 02:24:09 -0500
with message-id <[EMAIL PROTECTED]>
and subject line properly closing bugs "fixed" by NMU by sponsor
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: fail2ban
Version: 0.6.0-3
Severity: normal
It seems like fail2ban creates it's logfile only belonging to root. I
wonder if it shouldn't be readable by the 'adm'-group like
/var/log/auth.log for example.
I'm running Sarge, so I'm not sure if this has changed in unstable.
// Simon
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=sv_SE (charmap=ISO-8859-1)
Versions of packages fail2ban depends on:
ii iptables 1.2.11-10 Linux kernel 2.4+ iptables adminis
ii python 2.3.5-2 An interactive high-level object-o
-- no debconf information
--- End Message ---
--- Begin Message ---
Learn something new every day. Since I have not listed my respectful
Sponsor as an Uploader, all bugs which I was going to close were just
marked as fixed. Now I am properly closing the bugs
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
pgpR4v1I90n5B.pgp
Description: PGP signature
--- End Message ---
