Re: new debian patches

Willi Mann:
> Hi,
> 
> I added a few new patches for the latest upload of the debian logwatch
> package. You can find them at:
> 
> http://anonscm.debian.org/cgit/collab-maint/logwatch.git/tree/debian/patches
> 
> The patches that are new and I think would be interesting to add are:
> 
> 0004-Change-spamassassin-to-use-maillog-config.patch
commited: rev210 
 
> 0005-logfiles-vsftpd.conf-Use-custom-pattern-for-applystd.patch
Default syslog does not print a year. So this would break the filter on many 
machines.

> 0007-s-sshd-ignore-PAM-service-sshd-ignoring-max-retries-.patch
commited: rev 211

> 0008-s-s-exim-Fix-wrong-regex.patch
commited: rev 212

> 0009-s-s-sshd-Support-fatal-Write-failed-Connection-reset.patch
commited: rev 213

> 0010-s-s-dovecot-Recognize-and-report-Server-shutting-dow.patch
commited: rev 214

> 0011-s-s-pam_unix-Fix-two-unknown-entries.patch
commited: rev 215


> The patch
> 
> 0006-Deb-specific-Print-full-path-to-freshclam-log.patch
> 
> is a hack that I think only makes sense on Debian where we know the
> default location of freshclam.log. I think it would be nice if service
> scripts could get the list of logfiles that triggered their invocation,
> but AFAIK this does not exist yet, right?

I have attached a rough patch which makes a space separated list of 
logfiles/archives available via LOGWATCH_{LOGFILE,ARCHIVE}_LIST envionment 
variable. Do you think this would be usefull?

> thanks
> WM

Regards
Stefan



------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk