Willi Mann wrote:
This says LOG_ERR, and I don't think we should kill error messages.
However, it would make sense to summarise it, to avoid differnent
process numbers to make the list of Unmatched Entries longer.
Superfluous non-error messages reported against libnss-mysql as bug
#390972:
Andreas Beckmann schrieb:
Package: logwatch
Version: 7.3.1-2
Severity: normal
Hi,
postfix-mysql and lib-nss-mysql spit out a few messages that are not
recognized in the secure log script. I added the following lines to
scripts/services/secure in order to ignore these messages:
or
Willi Mann wrote:
Will postfix/smtpd report anything useful to the secure logfile? If not,
we should ignore it completely.
postfix/smtpd messages from auth.log (user/domain info obscured and ran
though sort | uniq -c | sort -n):
113 sql plugin create statement from cmusaslsecretCRAM-MD5
postfix/smtpd messages from auth.log (user/domain info obscured and ran
though sort | uniq -c | sort -n):
113 sql plugin create statement from cmusaslsecretCRAM-MD5 user
example.com
115 sql plugin create statement from userPassword user example.com
126 begin transaction
Willi Mann wrote:
I have looked at the source code of libnns-mysql. The only occurence of
above message seems to be src/ent.c, line 202:
_nss_mysql_log(LOG_ERR,setent(%d): conf file parsing failed,
This says LOG_ERR, and I don't think we should kill error messages.
However, it would
Package: logwatch
Version: 7.3.1-2
Severity: normal
Hi,
postfix-mysql and lib-nss-mysql spit out a few messages that are not
recognized in the secure log script. I added the following lines to
scripts/services/secure in order to ignore these messages:
or ( $ThisLine =~
6 matches
Mail list logo
