logcheck 1.3.16ubuntu0.1 source package in Ubuntu
Changelog
logcheck (1.3.16ubuntu0.1) trusty; urgency=medium * ignore.d.server/dhclient: rewrite rules (Closes LP: #1357880) -- Joshua Powers <email address hidden> Mon, 24 Jul 2017 12:49:46 -0700
Upload details
- Uploaded by:
- Joshua Powers
- Sponsored by:
- Nish Aravamudan
- Uploaded to:
- Trusty
- Original maintainer:
- Ubuntu Developers
- Architectures:
- all
- Section:
- admin
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Trusty | updates | main | admin |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| logcheck_1.3.16ubuntu0.1.tar.xz | 128.2 KiB | 3dd01966f4b6711e4effff878d6bb1a3237f0587ae7bf848b83cab7ece5fb208 |
| logcheck_1.3.16ubuntu0.1.dsc | 1.8 KiB | 480b5f3e93081427b475f519054c933fc7b5f25bc6a43705060a8da08e939acd |
Available diffs
Binary packages built by this source
- logcheck: mails anomalies in the system logfiles to the administrator
Logcheck helps spot problems and security violations in your logfiles
automatically and will send the results to you in e-mail.
.
Logcheck was part of the Abacus Project of security tools, but this
version has been rewritten.
- logcheck-database: database of system log rules for the use of log checkers
This database is part of the Logcheck package, but might be used by others.
It brings a database of regular expressions for matching system log entries
after various criteria.
- logtail: Print log file lines that have not been read (deprecated)
This program will read in a standard text file and create an
offset marker when it reads the end. The offset marker is read
the next time logtail is run and the text file pointer is moved
to the offset location. This allows logtail to read in the next
lines of data following the marker. This is good for marking log
files for automatic log file checkers to monitor system events.
.
The package also provides logtail2, which better deals with rotated log
files: If logtail2 finds that the inode of the file was changed, it assumes
that the log has been rotated, and tries to find the file it was rotated to
using heuristic plugins. If it finds the file, it will print the remainder of
the file starting at the offset saved to the offset file. If a file with the
correct inode was not found, logtail2 will only print the new file in its
entirety before writing a new offset file.
