logcheck 1.3.24 source package in Ubuntu

Changelog

logcheck (1.3.24) unstable; urgency=medium

  * Bump Standards-Version to 4.6.0 no changes needed.
  * Thank you everyone and particular to Hannes von Haugwitz for
    maintaining this software (Closes: #981446).

 -- Jose M Calhariz <email address hidden>  Thu, 14 Jul 2022 21:09:03 +0100

Upload details

Uploaded by:
Debian logcheck Team
Uploaded to:
Sid
Original maintainer:
Debian logcheck Team
Architectures:
all
Section:
admin
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Kinetic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
logcheck_1.3.24.dsc 1.7 KiB 11fba53262b4547c5aa1f22955b5d69a1d099602488eb6cc8063eb0ebba9b008
logcheck_1.3.24.tar.xz 130.1 KiB 5e304adf2880967c3b155bcf98e4f0809417a16bf91adb372fa065f38ab2c0cf

Available diffs

No changes file available.

Binary packages built by this source

logcheck: check the system log for unusual entries

 Logcheck analyses the system log for unuexpected entries that could
 indicate problems or security issues.
 .
 Log entries in the system log (produced by systemd-journald, rsyslog
 or another system-log-dameon) are checked against a customisable
 database of regular expressions (such as that provided by the
 logcheck-database package) to identify routine messages: anything
 that does not identified as routine is reported to the system
 administrator.
 .
 Logcheck was originally part of the Abacus Project of security tools,
 but has been rewritten.

logcheck-database: database of system log rules for logcheck

 This package brings a database of regular expressions for matching
 system log entries. It is part of Logcheck, but might be used by
 other log checkers.

logtail: Identify new lines added to the end of log files

 Each time logtail and logtail2 are run on a file they print lines
 added since the last run.
 .
 They can be used by log checkers, such as logcheck, to identify new
 entries in log files.
 .
 This package provides both logtail and logtail2. The latter is better
 suited to log files that may be rotated between runs: if logtail2
 finds that the inode of the file changed, it tries to find the file
 it was rotated from using customisable heuristics. If it finds the
 file, it will new find lines added to the old file as well as to the
 new file.