search for: grootheest

Displaying 7 results from an estimated 7 matches for "grootheest".

2008 Mar 14
5
Bug#470929: dhcp: interface names can have dash in them
Package: logcheck-database Version: 1.2.54 Severity: normal I recently created a bridge with the name xen-local. The DHCP server gets requests via this bridge. I got spammed with logcheck messages about DHCPREQUESTS and the lot because the name of the interface in the logcheck-database does not match on names with a dash in it. -- System Information: Debian Release: 4.0 APT prefers stable
2008 Oct 21
3
Bug#503000: logcheck fails due to a perl warning
Package: logcheck Version: 1.2.68 Severity: important I upgraded my lenny server today. I guess the previous update is something like two weeks ago. Now logcheck started sending mails containing only this perl error: This email is sent by logcheck. If you wish to no-longer receive it, you can either deinstall the logcheck package or modify its configuration file (/etc/logcheck/logcheck.conf).
2005 Sep 07
3
Samba PDC (3.0.14a) with LDAP cannot add machines
...but I can share sections with interested developers. If there is other information that is useful, please just ask. Has this been fixed already and did I miss it in the releasenotes? Is there a work-around that I can use? This has been filed as 3064 with the samba bugzilla. Thanks, Jan Evert van Grootheest
2010 Dec 29
1
Bug#608256: /etc/logcheck/ignore.d.server/dnsmasq: dnsmasq: interface names are allowed to have a dash (-) please add this to the filter
Package: logcheck-database Version: 1.2.69 Severity: normal File: /etc/logcheck/ignore.d.server/dnsmasq A dnsmasq log about DHCP events has the interface name in it. Interface names are allowed to have a dash (-) in them, but the logcheck filter does not have the dash in it. Please add the dash. -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500,
2009 Jan 02
1
Bug#510472: logcheck-database: pam_unix messages could be ignored.
Package: logcheck-database Version: 1.2.68 Severity: normal I'm using ldap to authenticate users. And thus pam_unix is sufficient, but allowed to fail. It has now started to spam the logs with lots of Jan 2 09:22:57 sisko sshd[28511]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=host92-22-static.38-79-b.business.telecomitalia.it user=root And on
2002 Jul 23
1
strange files appearing after file copy
Hello, I just had something strange happen and could not find explanations in the documentation, FAQs or mailing list. The server is a Debian installation running Samba 2.2.3 (kernel 2.4.18 if interested). It has been recently upgraded from 2.0.x (I think x=6). My smb.conf is at the bottom; the directory used is on the [public] share. The client runs Win2k (probably SP2). I copied some files in
2006 Oct 31
0
Bug#396407: logcheck-database: Amandad line not ignored.
Package: logcheck-database Version: 1.2.47 Severity: normal The ignore.d.server/amandad file only ignores connections from hosts that cannot be found in DNS. My hosts are found in DNS, resulting in connection reports including host names as well as IP addresses. I would like to ask that connections to amandad with a hostname also be ignored. Below is an example of such a log (changed the hostname