thr3ads.net - Logcheck devel - [Logcheck-devel] Bug#270018: logcheck-database: add Hylafax support [Sep 2004]

If this information is useful, please help other people find it:
Share via:

Ross Boylan

2004-Sep-04 22:36 UTC

[Logcheck-devel] Bug#270018: logcheck-database: add Hylafax support

Package: logcheck-database
Version: 1.2.25
Severity: wishlist

It would be nice to add rules filtering out the typical messages from
hylafax, including its faxgetty program.  As a starting point, here
are the rules I use:

# this line is too specific, since it depends on my model of modem
FaxGetty\[[[:digit:]]+\]: +MODEM U.S. ROB
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ +FaxGetty\[[[:digit:]]+\]: +[._[:alnum:]-]+
modem: disable Class
FaxGetty\[[[:digit:]]+\]: +STATE CHANGE:
FaxGetty\[[[:digit:]]+\]: +ANSWER:
FaxGetty\[[[:digit:]]+\]: +CLOSE

FaxQueuer\[[[:digit:]]+\]: +FIFO RECV
# the modem device need not be ttySn, I think
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +READY,
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +BUSY
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +DOWN

I put all these in server.  Conceivably ANSWER, BUSY, and DOWN might
be more appropriate in workstation level.  The "disable Class" message
might belong there too, though it's the result of something I put in
the config file, and so is not very interesting.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages logcheck-database depends on:
ii  debconf [debconf-2.0]         1.4.30.2   Debian configuration management sy

-- debconf information:
* logcheck-database/rules-directories-note:
* logcheck-database/standard-rename-note:
* logcheck-database/conffile-cleanup: true
* logcheck-database/security_level: workstation

maks attems

2004-Sep-18 22:25 UTC

head link

Bug#270018: [Logcheck-devel] Bug#270018: logcheck-database: add Hylafax support

On Sat, 04 Sep 2004, Ross Boylan wrote:
> Package: logcheck-database
> Version: 1.2.25
> Severity: wishlist
> 
> It would be nice to add rules filtering out the typical messages from
> hylafax, including its faxgetty program.  As a starting point, here
> are the rules I use:
> 
> # this line is too specific, since it depends on my model of modem
> FaxGetty\[[[:digit:]]+\]: +MODEM U.S. ROB
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ +FaxGetty\[[[:digit:]]+\]:
+[._[:alnum:]-]+ modem: disable Class
> FaxGetty\[[[:digit:]]+\]: +STATE CHANGE:
> FaxGetty\[[[:digit:]]+\]: +ANSWER:
> FaxGetty\[[[:digit:]]+\]: +CLOSE
those rules are far too generic to be included in the main package!

when sending in rules please read:
 /usr/share/doc/logcheck-database/README.logcheck-database.gz
if not the apropriate logmessages also helps.

#270019 has same unanswered request.

Debian Bug Tracking System

2004-Oct-02 10:48 UTC

head link

[Logcheck-devel] Bug#270018: marked as done (logcheck-database: add Hylafax support)

Your message dated Sat, 2 Oct 2004 12:30:44 +0200
with message-id <20041002103044.GA1777 at stro.at>
and subject line hylafax rules
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Sep 2004 22:36:11
+0000>From RossBoylan at stanfordalumni.org Sat Sep 04 15:36:11 2004Return-path: <RossBoylan at stanfordalumni.org>
Received: from gull.mail.pas.earthlink.net [207.217.120.84] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1C3j8k-0005c1-00; Sat, 04 Sep 2004 15:36:11 -0700
Received: from dialup-4.243.230.125.dial1.sanfrancisco1.level3.net
([4.243.230.125] helo=wheat.dslnorthwest.net)
	by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 1C3j8j-0002OL-00; Sat, 04 Sep 2004 15:36:10 -0700
Received: from ross by wheat.dslnorthwest.net with local (Exim 3.36 #1 (Debian))
	id 1C3j8i-0005c4-00; Sat, 04 Sep 2004 15:36:08 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ross Boylan <RossBoylan at stanfordalumni.org>
To: Debian Bug Tracking System <submit at bugs.debian.org>
CC: RossBoylan at stanfordalumni.org
Subject: logcheck-database: add Hylafax support
X-Mailer: reportbug 2.63
Date: Sat, 04 Sep 2004 15:36:07 -0700
Message-Id: <E1C3j8i-0005c4-00 at wheat.dslnorthwest.net>
Sender: Ross Boylan <RossBoylan at stanfordalumni.org>
Delivered-To: submit at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: logcheck-database
Version: 1.2.25
Severity: wishlist

It would be nice to add rules filtering out the typical messages from
hylafax, including its faxgetty program.  As a starting point, here
are the rules I use:

# this line is too specific, since it depends on my model of modem
FaxGetty\[[[:digit:]]+\]: +MODEM U.S. ROB
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ +FaxGetty\[[[:digit:]]+\]: +[._[:alnum:]-]+
modem: disable Class
FaxGetty\[[[:digit:]]+\]: +STATE CHANGE:
FaxGetty\[[[:digit:]]+\]: +ANSWER:
FaxGetty\[[[:digit:]]+\]: +CLOSE

FaxQueuer\[[[:digit:]]+\]: +FIFO RECV
# the modem device need not be ttySn, I think
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +READY,
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +BUSY
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +DOWN

I put all these in server.  Conceivably ANSWER, BUSY, and DOWN might
be more appropriate in workstation level.  The "disable Class" message
might belong there too, though it's the result of something I put in
the config file, and so is not very interesting.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages logcheck-database depends on:
ii  debconf [debconf-2.0]         1.4.30.2   Debian configuration management sy

-- debconf information:
* logcheck-database/rules-directories-note:
* logcheck-database/standard-rename-note:
* logcheck-database/conffile-cleanup: true
* logcheck-database/security_level: workstation

---------------------------------------
Received: (at 270018-done) by bugs.debian.org; 2 Oct 2004 10:30:32
+0000>From max at stro.at Sat Oct 02 03:30:32 2004Return-path: <max at stro.at>
Received: from baikonur.stro.at [213.239.196.228] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CDh9s-0007BE-00; Sat, 02 Oct 2004 03:30:32 -0700
Received: from localhost (localhost [127.0.0.1])
	by baikonur.stro.at (Postfix) with ESMTP id 88F915C06C
	for <270018-done at bugs.debian.org>; Sat,  2 Oct 2004 12:30:29 +0200
(CEST)
Received: from baikonur.stro.at ([127.0.0.1])
	by localhost (baikonur [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 15216-04 for <270018-done at bugs.debian.org>;
	Sat, 2 Oct 2004 12:30:29 +0200 (CEST)
Received: from sputnik (stallburg.stro.at [128.131.216.190])
	by baikonur.stro.at (Postfix) with ESMTP id 2AAE85C034
	for <270018-done at bugs.debian.org>; Sat,  2 Oct 2004 12:30:29 +0200
(CEST)
Received: from max by sputnik with local (Exim 4.34)
	id 1CDhA4-0000gC-HD
	for 270018-done at bugs.debian.org; Sat, 02 Oct 2004 12:30:44 +0200
Date: Sat, 2 Oct 2004 12:30:44 +0200
From: maks attems <debian at sternwelten.at>
To: 270018-done at bugs.debian.org
Subject: hylafax rules
Message-ID: <20041002103044.GA1777 at stro.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040722i
Sender: maximilian attems <max at stro.at>
X-Virus-Scanned: by Amavis (ClamAV) at stro.at
Delivered-To: 270018-done at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

closing, please follow README.logcheck-database.gz the next time
and or post the loglines without the startup noise.

--
maks

Debian Bug Tracking System

2004-Nov-09 09:03 UTC

head link

[Logcheck-devel] Bug#270018: marked as done (logcheck-database: add Hylafax support)

Your message dated Tue, 09 Nov 2004 03:47:03 -0500
with message-id <E1CRReZ-0006ao-00 at newraff.debian.org>
and subject line Bug#270018: fixed in logcheck 1.2.31
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Sep 2004 22:36:11
+0000>From RossBoylan at stanfordalumni.org Sat Sep 04 15:36:11 2004Return-path: <RossBoylan at stanfordalumni.org>
Received: from gull.mail.pas.earthlink.net [207.217.120.84] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1C3j8k-0005c1-00; Sat, 04 Sep 2004 15:36:11 -0700
Received: from dialup-4.243.230.125.dial1.sanfrancisco1.level3.net
([4.243.230.125] helo=wheat.dslnorthwest.net)
	by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 1C3j8j-0002OL-00; Sat, 04 Sep 2004 15:36:10 -0700
Received: from ross by wheat.dslnorthwest.net with local (Exim 3.36 #1 (Debian))
	id 1C3j8i-0005c4-00; Sat, 04 Sep 2004 15:36:08 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ross Boylan <RossBoylan at stanfordalumni.org>
To: Debian Bug Tracking System <submit at bugs.debian.org>
CC: RossBoylan at stanfordalumni.org
Subject: logcheck-database: add Hylafax support
X-Mailer: reportbug 2.63
Date: Sat, 04 Sep 2004 15:36:07 -0700
Message-Id: <E1C3j8i-0005c4-00 at wheat.dslnorthwest.net>
Sender: Ross Boylan <RossBoylan at stanfordalumni.org>
Delivered-To: submit at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: logcheck-database
Version: 1.2.25
Severity: wishlist

It would be nice to add rules filtering out the typical messages from
hylafax, including its faxgetty program.  As a starting point, here
are the rules I use:

# this line is too specific, since it depends on my model of modem
FaxGetty\[[[:digit:]]+\]: +MODEM U.S. ROB
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ +FaxGetty\[[[:digit:]]+\]: +[._[:alnum:]-]+
modem: disable Class
FaxGetty\[[[:digit:]]+\]: +STATE CHANGE:
FaxGetty\[[[:digit:]]+\]: +ANSWER:
FaxGetty\[[[:digit:]]+\]: +CLOSE

FaxQueuer\[[[:digit:]]+\]: +FIFO RECV
# the modem device need not be ttySn, I think
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +READY,
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +BUSY
FaxQueuer\[[[:digit:]]+\]: +MODEM ttyS[[:digit:]]: +DOWN

I put all these in server.  Conceivably ANSWER, BUSY, and DOWN might
be more appropriate in workstation level.  The "disable Class" message
might belong there too, though it's the result of something I put in
the config file, and so is not very interesting.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages logcheck-database depends on:
ii  debconf [debconf-2.0]         1.4.30.2   Debian configuration management sy

-- debconf information:
* logcheck-database/rules-directories-note:
* logcheck-database/standard-rename-note:
* logcheck-database/conffile-cleanup: true
* logcheck-database/security_level: workstation

---------------------------------------
Received: (at 270018-close) by bugs.debian.org; 9 Nov 2004 08:53:24
+0000>From katie at ftp-master.debian.org Tue Nov 09 00:53:23 2004Return-path: <katie at ftp-master.debian.org>
Received: from newraff.debian.org [208.185.25.31] (mail)
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CRRkh-0007cI-00; Tue, 09 Nov 2004 00:53:23 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
	id 1CRReZ-0006ao-00; Tue, 09 Nov 2004 03:47:03 -0500
From: Todd Troxell <ttroxell at debian.org>
To: 270018-close at bugs.debian.org
X-Katie: $Revision: 1.51 $
Subject: Bug#270018: fixed in logcheck 1.2.31
Message-Id: <E1CRReZ-0006ao-00 at newraff.debian.org>
Sender: Archive Administrator <katie at ftp-master.debian.org>
Date: Tue, 09 Nov 2004 03:47:03 -0500
Delivered-To: 270018-close at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Source: logcheck
Source-Version: 1.2.31

We believe that the bug you reported is fixed in the latest version of
logcheck, which is due to be installed in the Debian FTP archive:

logcheck-database_1.2.31_all.deb
  to pool/main/l/logcheck/logcheck-database_1.2.31_all.deb
logcheck_1.2.31.dsc
  to pool/main/l/logcheck/logcheck_1.2.31.dsc
logcheck_1.2.31.tar.gz
  to pool/main/l/logcheck/logcheck_1.2.31.tar.gz
logcheck_1.2.31_all.deb
  to pool/main/l/logcheck/logcheck_1.2.31_all.deb
logtail_1.2.31_all.deb
  to pool/main/l/logcheck/logtail_1.2.31_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 270018 at bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Todd Troxell <ttroxell at debian.org> (supplier of updated logcheck
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster at debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tuesday, 09 Nov 2004 03:25:11 -0500
Source: logcheck
Binary: logcheck logtail logcheck-database
Architecture: source all
Version: 1.2.31
Distribution: unstable
Urgency: low
Maintainer: Debian logcheck Team <logcheck-devel at
lists.alioth.debian.org>
Changed-By: Todd Troxell <ttroxell at debian.org>
Description: 
 logcheck   - Mails anomalies in the system logfiles to the administrator
 logcheck-database - A database of system log rules for the use of log checkers
 logtail    - Print log file lines that have not been read
Closes: 270018 279635
Changes: 
 logcheck (1.2.31) unstable; urgency=low
 .
   jamie
   * Fix rules for hylafax, thanks to Ross Boylan. (closes: #270018)
   max
   * Add rule for tripwire run at level paranoid.
   * Add rule for nscd at level server.
   alfie:
   * Fixed my non-fix in logcheck, sorry (closes: #279635)
   todd:
   * Fix segmented rules, thanks rloboda at bojko.krakow.pl
Files: 
 b753d6aa552144af9f0413ae10daacfd 703 admin optional logcheck_1.2.31.dsc
 f14efaf0494e4a2ce2840cfd8d7cf205 86528 admin optional logcheck_1.2.31.tar.gz
 e2fb0d8cecf58b65de828cb42a6dd52f 40604 admin optional logcheck_1.2.31_all.deb
 1a502877f44cb18a359d125b5f00c608 53990 admin optional
logcheck-database_1.2.31_all.deb
 d41144f2933fa425069885a824104dfb 24186 admin optional logtail_1.2.31_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBkH9v4u3oQ3FHP2YRAgTGAJ9zpLBfK0WrgvHVUcBO0Xqrw407aACeIu0f
ikZMIHxu3cJ1tSZQYBvbMyQ=aWG+
-----END PGP SIGNATURE-----

Logcheck devel - Sep 2004 - Bug#270018: logcheck-database: add Hylafax support

[Logcheck-devel] Bug#270018: logcheck-database: add Hylafax support

Bug#270018: [Logcheck-devel] Bug#270018: logcheck-database: add Hylafax support

[Logcheck-devel] Bug#270018: marked as done (logcheck-database: add Hylafax support)

[Logcheck-devel] Bug#270018: marked as done (logcheck-database: add Hylafax support)