Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

logtail(8) [debian man page]

LOGTAIL(8)							  logtail manual							LOGTAIL(8)

NAME
logtail - print log file lines that have not been read SYNOPSIS
logtail [-t] -flogfile [-ooffsetfile] DESCRIPTION
logtail reads a specified file (usually a log file) and writes to the standard output that part of it which has not been read by previous runs of logtail. It prints the appropriate number of bytes from the end of logfile, assuming that all changes that are made to it are to add new characters to it. logfile must be a plain file. A symlink is not allowed. logtail stores the information about how much of it has already been read in a separate file called offsetfile. offsetfile can be omitted. If omitted, the file named logfile.offset in the same directory which contains logfile is used by default. If offsetfile is not empty, the inode of logfile is checked. If the inode is changed, logtail simply prints the entire file. If the inode is not changed but logfile is shorter than it was at the last run of logtail, it writes a warning message to the standard output. OPTIONS
-f logfile to be read after offset -o offsetfile stores offset of previous run -t test mode - do not change offset in offsetfile RETURN VALUES
0 successful 65 cannot get the size of logfile 66 logfile does not exist, is not a plain file, or is not readable 73 cannot write offsetfile AUTHOR
The original logtail was written in C by Craig H. Rowland <crowland@psionic.com>. This version of logtail is a Perl reimplementation by Paul Slootman <paul@debian.org>. Enhanced by the Debian Logcheck Team <logcheck-devel@lists.alioth.debian.org>. This manual was written by Oohara Yuuma <oohara@libra.interq.or.jp>. SEE ALSO
logcheck(8) Debian Fri, 19 Nov 2004 LOGTAIL(8)

Check Out this Related Man Page

Logcheck(8)						      System Manager's Manual						       Logcheck(8)

NAME
logcheck -- program to scan system logs for interesting lines SYNOPSIS
logcheck [OPTIONS] DESCRIPTION
The logcheck program helps spot problems and security violations in your logfiles automatically and will send the results to you periodi- cally in an e-mail. By default logcheck runs as an hourly cronjob just off the hour and after every reboot. logcheck supports three level of filtering: "paranoid" is for high-security machines running as few services as possible. Don't use it if you can't handle its verbose messages. "server" is the default and contains rules for many different daemons. "workstation" is for shel- tered machines and filters most of the messages. The ignore rules work in additive manner. "paranoid" rules are also included at level "server". "workstation" level includes both "paranoid" and "server" rules. The messages reported are sorted into three layers, system events, security events and attack alerts. The verbosity of system events is controlled by which level you choose, paranoid, server or workstation. However, security events and attack alerts are not affected by this. EXAMPLES
logcheck can be invoked directly thanks to su(8) or sudo(8), which change the user ID. The following example checks the logfiles without updating the offset and outputs everything to STDOUT. sudo -u logcheck logcheck -o -t OPTIONS
A summary of options is included below. -c CFG Overrule default configuration file. -d Debug mode. -h Show usage information. -H Use this hostname string in the subject of logcheck mail. -l LOG Run logfile through logcheck. -L CFG Overrule default logfiles list. -m Mail report to recipient. -o STDOUT mode, not sending mail. -p Set the report level to "paranoid". -r DIR Overrule default rules directory. -R Adds "Reboot:" to the email subject line. -s Set the report level to "server". -S DIR Overrule default state directory. -t Testing mode does not update offset. -T Do not remove the TMPDIR. -u Enable syslog-summary. -v Print current version. -w Set the report level to "workstation". FILES
/etc/logcheck/logcheck.conf is the main configuration file. /etc/logcheck/logcheck.logfiles is the list of files to monitor. /usr/share/doc/logcheck-database/README.logcheck-database.gz for hints on how to write, test and maintain rules. EXIT STATUS
0 upon success; 1 upon failure SEE ALSO
logtail(8) AUTHOR
logcheck is developed by Debian logcheck Team at alioth: http://alioth.debian.org/projects/logcheck/. This manual page was written by Jon Middleton. Logcheck(8)
Man Page