Displaying 20 results from an estimated 26 matches for "newraff".
Did you mean:
newcaf
2005 Jan 20
2
Bug#291395: logcheck-database: Rules dirs are setuid, they should be setgid
Package: logcheck-database
Version: 1.2.33
Severity: normal
I just installed 1.2.33, and it made my rules dirs setuid, not setgid...
- Marc
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
Versions of
2004 Aug 31
1
Bug#269318: logcheck: /etc/logcheck/ignore.d.server (add spamassassin)
Package: logcheck
Version: 1.2.26
Severity: wishlist
Please add ignore for Spamassasin's "check" messages like:
Aug 16 19:27:54 ns spamd[23853]: checking message <20040816150710.86ADA708A8 at smtp-out.hotpop.com> for nobody:65534.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.26.20040601
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL
2005 Jan 09
2
Bug#289529: logcheck: "Ghandi" should be "Gandhi" in README.how.to.interpret
Package: logcheck
Version: 1.2.32
Severity: minor
"Ghandi" should be "Gandhi" in README.how.to.interpret, assuming that
you mean the Indian freedom fighter M.K. Gandhi a.k.a. Mahatma Gandhi.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=C, LC_CTYPE=C
2004 Oct 21
3
Bug#277636: logcheck-database: support for dnsmasq
Package: logcheck-database
Version: 1.2.28
Severity: wishlist
Could you add support for dnsmasq for the server profile?
This is the standard dnsmasq output.
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dnsmasq\[[[:digit:]]+\]: read /etc/hosts - [[:digit:]]+ addresses$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dnsmasq\[[[:digit:]]+\]: reading /etc/resolv.conf$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2004 Sep 04
1
Bug#269959: logcheck-database: courier ignore.d.server contains word from violations.d list
Package: logcheck-database
Version: 1.2.26
Severity: normal
Hi,
the file courier contains the line:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ pop3d-ssl: Unexpected SSL connection
shutdown\.$
This triggers the security logcheck section because of the word
"shutdown". Quick fix is to move or duplicate this line to
violations.ignore.d/logcheck-courier.
BTW: It looks like the courier package
2005 Jan 11
2
Bug#289801: Logtail should output error messages to stderr, not stdout
Package: logtail
Version: 1.2.33
Severity: normal
Hi...
Logtail should not output error messages to standard output, since this
violates the principle of least surprise.
In particular, my application was broken by the semantics of logtail changing
in version 1.2.21 (when you added switches for the default arguments to
logtail). I think this was a bad move -- you broke an interface used by
2005 Mar 06
3
Bug#298291: logcheck-database: Printer out-of-paper reported
Package: logcheck-database
Version: 1.2.34
Severity: minor
I have parallel port attached printer and kernel reports whenever
printer is out of paper:
Mar 6 12:38:50 host kernel: lp0 out of paper
However, this is not a situation that should be reported by default
(IMHO) by logcheck sending report email. Thus I propose adding
following line to ignore.d.workstation/logcheck (possibly to .server
2004 Aug 23
2
Bug#267587: logcheck-database: Additional rule needed for postfix
Package: logcheck-database
Version: 1.2.25
Severity: normal
postfix/smtpd\[[0-9]+\]: lost connection after (CONNECT|DATA|RCPT|RSET|EHLO|HELO|MAIL) from
Please include the above line in the ignore.d/server/postfix file. That
catches messages that occur very often on busy Postfix servers.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
2005 Feb 12
3
Bug#294950: logcheck: ignore.d.server courier imaplogin: DISCONNECTED not matching
Package: logcheck
Version: 1.2.34
Severity: normal
the ignore.d.server pattern for courier 'imaplogin: DISCONNECTED' does
not match the following line:
Feb 12 16:19:47 backup imaplogin: DISCONNECTED,
user=example at example.com, ip=[::ffff:111.111.111.111],
headers=14013, body=0, time=1
This line should be ignored like the other DISCONNECTED messages. Or am
I wrong?
-- System
2005 Apr 02
3
Bug#302744: logcheck-database: postfix rules
Package: logcheck-database
Version: 1.2.36
Severity: wishlist
Hello,
I recently blew away my old logcheck-databse and lost a number of changes that i had made to postfix entries. The default database for postfix reports the
following errors that do not seem to be important...
Apr 2 13:00:19 terminus postfix/local[29516]: 574B9B3B9F: to=<doug at localhost>, relay=local, delay=13,
2004 Sep 12
2
Bug#271286: minor fix for ignore.d.server/oidentd
Package: logcheck
Version: 1.2.27
Severity: wishlist
hello,
in ignore.d.server/oidentd you have:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ oidentd\[[0-9]+\]: Connection from \
[._[:alnum:]-]+ \([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\):[0-9]{1,5}$
anyway, some oidentd logs don't have a hostname:
oidentd[34562]: Connection from 241.145.24.135:2353
therefore you have to add:
^\w{3} [
2005 Jan 14
3
Bug#290511: logcheck: syslogd restart in cron.daily/sysklogd causes a log message
Package: logcheck
Version: 1.2.32
Severity: wishlist
/etc/cron.daily/sysklogd restarts syslogd at the end of the script.
This causes a daily log message, currently missed by logcheck:
Jan 14 06:55:22 pyloric syslogd 1.4.1#16: restart (remote reception).
I'm currently using this regex in ignore.server.d/local-syslogd:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd 1\.4\.1#16: restart \(remote
2004 Dec 20
3
Bug#286532: dnsmasq: misses message for DHCPINFORM due to 283331 fix
Package: logcheck-database
Version: 1.2.32
Severity: normal
Tags: patch
The fix for 283331 exposed a bug in the dnsmasq rules. The rule was
looking for DHCPINFO, but the actual message is DHCPINFORM. Prior to
the 283331 fix, the old rule worked, because the "[()[:alnum:]]+" part
of the rule matched the "RM" at the end of DHCPINFORM.
-- System Information:
Debian Release:
2004 Nov 21
2
Bug#282378: logcheck-database: messages from USB joystick use
Package: logcheck-database
Version: 1.2.31
Severity: wishlist
The following is reported by logcheck when inserting a USB joystick for
the first time (workstation), none of which (I assume) I need to be
informed of.
Nov 21 17:50:08 localhost kernel: ohci_hcd 0000:00:01.2: wakeup
Nov 21 17:50:08 localhost kernel: usb 1-1: new low speed USB device using address 2
Nov 21 17:50:10 localhost kernel:
2004 Dec 25
2
Bug#287184: logcheck overwriting ownership/permissions of /etc/logcheck/* on upgrades
Package: logcheck
Version: 1.2.32
Severity: important
In postinst logcheck "fixes" permissions of /etc/logcheck/* to 750.
In my (and others on #d-d) opinion ownership and permissions should be
preserved upon package upgrades. Logcheck must not screw with my
decision to make them world readable every time it configures.
--
Peter
2004 Oct 13
2
Bug#276317: logcheck-database: Namechange for ISC in /etc/logcheck/ignore.d.server/dhcp
Package: logcheck-database
Version: 1.2.28
Severity: normal
Hi,
the Internet Software Consortium changed the name to Internet Systems Consortium.
For a fix for the logcheck rules see the attachment.
-- System Information:
Debian Release: 3.0
APT prefers testing
APT policy: (600, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel:
2004 Jun 04
2
Bug#252597: logcheck: user logchecks mails should be delivered to root
Package: logcheck
Version: 1.2.20a
Severity: important
Since logcheck changed to run as user logcheck, the error mails of the cron
daemon end up in /var/mail/logcheck where nobody reads them. Mails for
logcheck should be aliased to root like all the other mails of system
accounts.
I was searching for a long time what was wrong with my logcheck not
delivering any mails. The lock directory was
2005 Jan 12
3
Bug#290195: violations.d/sudo and violations.ignore.d/logcheck-sudo missing sudo log entries
Package: logcheck
Version: 1.2.32
Severity: normal
It seems when someone runs a sudo command on my system, logcheck misses
it.
The second line of /etc/logcheck/violations.d/sudo matches them, but
the /etc/logcheck/violations.ignore.d/logcheck-sudo kills them.
Furthermore, when users run commands like '$ sudo rm *' in a directory
with lots of files, we reports with lines like:
Jan 13
2005 Apr 26
3
Bug#306388: add ignore line for udhcpd
Package: logcheck-database
Severity: wishlist
Hi,
the following two lines should be added either to ignore.d.server/dhcp or
ignore.d.server/udhcp to ignore messages from udhcpd (other lines may be
necessary)
# udhcpd support
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ udhcpd\[[0-9]+\]: sending OFFER of [.0-9]+
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ udhcpd\[[0-9]+\]: sending ACK to [.0-9]+
filippo
2004 Jul 21
4
Bug#260743: logcheck-database: dhcp rule updates for failover support
Package: logcheck-database
Version: 1.2.23
Severity: minor
Hi,
a couple of minor corrections to the dhcp rule sets:
First of all, the hostname matching parts need to include the "._-"
signs (maybe . is not needed but it might be).
Then when using failover, log lines of type DHCPDISCOVER and DHCPREQUEST
may be entailed by the string ": load balance to peer <somestring>".