Displaying 20 results from an estimated 6000 matches similar to: "Bug#270019: 270018, 270019 should remain open"
2004 Sep 06
2
Bug#270019: serial/lp rules for logcheck
At the moment I've no host with which to test ppp/lp things on. If you (or
anyone) could provide complete regexes, (each beginning with ^ and ending with
$) I will patch the rules accordingly.
If not, sending the full log lines is a good start.
Thanks!
--
[ Todd J. Troxell ,''`.
Student, Debian GNU/Linux Developer, SysAdmin, Geek :
2019 Jun 19
5
[RFC] Documentation clarification: Phabricator, not the lists is the main entry point for new patches
The current documentation talks about both the Phabricator review, and review
as mail replies on -commits lists. It also talks about submitting
patches to lists,
with the subtext that it may be friendlier for outsiders.
It is true that Phabricator has some entry threshold, larger than
github, or maillists,
so the attempt is not unwarranted. But from what i can tell, 99.9% patches go
via
2007 Oct 29
1
Bug#448510: logcheck-database: revised pattern for spamd
Package: logcheck-database
Version: 1.2.63
Severity: normal
Tags: patch
spamassassin is now reporting Unix domain sockets in the rport field.
I'm not exactly sure what changed to cause this to happen; it started
after an upgrade whose only remotely relevant package was razor.
I think the following pattern in ignore.d.server/spamd will work
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2006 Feb 22
2
Bug#353962: integrate courier file in logcheck-database
Package: courier-imap-ssl,logcheck-database
Severity: wishlist
Please move /etc/logcheck/*/courier to the courier packages and out
of logcheck-database.
-- System Information:
Debian Release: testing/unstable
APT prefers stable
APT policy: (700, 'stable'), (600, 'testing'), (98, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked
2004 May 25
2
Bug#222240: Ask for frequency during install (logcheck)
hello,
the debconf configuration of logcheck was removed since woody release:
as logcheck's user base is targeting server admins,
we don't see the need of a debconf based question regarding the
frequency of logcheck. beside once per day is a good default.
a note was added to documentation README.Debian that this value
may be changed in /etc/cron.d/logcheck.
so these bugreports will be
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
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 Jun 13
1
intermittent access this week
Hey team,
I'll be at sea on and off this week, and as such my Internet access will
depend on wifi availability while in port. 22a seems stable, but if any
critical problems arise, feel free to prepare a release and bug Alfie
to upload it.
On the brighter side, I expect to be extremely bored while offline so I'll
probably get some logcheck work done. <:
Cheers,
--
[ Todd J.
2004 Aug 31
1
Bug#269315: logcheck: /etc/logcheck/ignore.d.server (add bind9 messages)
Package: logcheck
Version: 1.2.26
Severity: wishlist
Please add following bind9 server messages to ignore: i.e from below,
everything that includex "zone.*loaded" + the other messages.
Aug 16 20:24:27 ns named[3350]: shutting down: flushing changes
Aug 16 20:24:27 ns named[3350]: stopping command channel on 127.0.0.1#953
Aug 16 20:24:27 ns named[3350]: stopping command channel on
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,
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 Jul 15
5
Bug#259603: logcheck-database: postfix/lmtp rules do not match some configurations
package: logcheck-database
version: 1.2.23
severity: wishlist
The current regexp's for postfix/lmtp..
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/lmtp\[[0-9]+\]: [0-9A-F]:
to=<[^[:space:]]+>, orig_to=<[^[:space:]]+>, relay=[^[:space:]]+\],
delay=[0-9]+ status=sent \(250 2\.1\.5 Ok\)$
..doesn't catch these messages:
Jul 15 17:15:16 lorien postfix/lmtp[17151]: C1170480008B:
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 Jun 14
3
Bug#313601: logcheck-database: ignore mount version messages
Package: logcheck-database
Version: 1.2.39
Severity: wishlist
These are the subject of an am-utils FAQ
<URL:http://www.am-utils.org/docs/am-utils/FAQ.txt> and would be
useful in the ignored list. Note that it's either `newer' or `older'.
Jun 14 14:32:25 albion kernel: nfs warning: mount version newer than kernel
Jun 14 14:37:54 dlsy kernel: nfs warning: mount version older
2004 Jun 03
1
4 important bugs again <;
hello everyone,
thanks to todd 1.2.21 is out :)
every release getting better, i would like to get
consensus on these "important" bugs:
#252078 logtail: should depend on perl >= 5.8
sarge as any other modern linux distro use perl 5.8.x,
it's even inside of its base.
backports are under the peril of its author
if no one voices up, i'll close that bug in the next days.
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:
2005 Feb 16
3
Bug#295560: logcheck: Please include filename when reporting "invalid regular expression"
Package: logcheck
Version: 1.2.34
Severity: wishlist
I have a couple of home-made logcheck ignore files, and happened to
have one unescaped (and unmatched) `(' in one of the filter
lines. Because of this, cron sent a mail with the body "grep: Invalid
regular expression" - the subject is the command in the "2 * * * *"
line in /etc/cron.d/logcheck, of course.
It would be
2009 Nov 06
2
Bug#554828: logcheck: Please include rules for amd (automount daemon from am-utils package)
Package: logcheck
Version: 1.3.3
Severity: wishlist
Tags: patch
Ali Saidi submitted rules for amd from the am-utils package to Ubuntu
at https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/91438
The provided rules are located at: http://launchpadlibrarian.net/6728953/amd
Please consider including them in the next release.
I've asked where to put them, but it should probably the
2005 Aug 31
3
Bug#325801: logcheck: new regex to filter imap "Moved xxx bytes of new mail" messages
Package: logcheck
Version: 1.2.41
Severity: wishlist
Hi folks, thanks for your work maintaining logcheck, it works well.
When my users read their mail using imap (usually via squirrelmail,
not sure about other clients) I get a message like this in the log:
Aug 22 21:03:32 phoenix imapd[6551]: Moved 11323 bytes of new mail to /home/winky/mail/mbox from /var/spool/mail/winky host= localhost
2015 Jul 01
4
[LLVMdev] C as used/implemented in practice: analysis of responses
On 1 July 2015 at 11:34, Russell Wallace <russell.wallace at gmail.com> wrote:
> Why do you say spin?
You're dismissing all use-cases other than this very narrow one I'd
(with my own spin) characterise as "Do What I Mean, I Can't Be
Bothered To Get My Code Right". Fair enough, you're arguing in favour
of a point; but it's not one I agree with.
Tim.