ipsec_barf(8) [centos man page]

IPSEC_BARF(8)							Executable programs						     IPSEC_BARF(8)

NAME

       ipsec_barf - spew out collected IPsec debugging information

SYNOPSIS

       ipsec barf [--short --maxlines <100>]

DESCRIPTION

       Barf outputs (on standard output) a collection of debugging information (contents of files, selections from logs, etc.) related to the
       IPsec encryption/authentication system. It is primarily a convenience for remote debugging, a single command which packages up (and labels)
       all information that might be relevant to diagnosing a problem in IPsec.

       The --short option limits the length of the log portion of barf's output, which can otherwise be extremely voluminous if debug logging is
       turned on.

       --maxlines <100> option sets the length of some bits of information, currently netstat -rn. Useful on boxes where the routing table is
       thousands of lines long. Default is 100.

       Barf censors its output, replacing keys and secrets with brief checksums to avoid revealing sensitive information.

       Beware that the output of both commands is aimed at humans, not programs, and the output format is subject to change without warning.

       Barf has to figure out which files in /var/log contain the IPsec log messages. It looks for KLIPS and general log messages first in
       messages and syslog, and for Pluto messages first in secure, auth.log, and debug. In both cases, if it does not find what it is looking for
       in one of those "likely" places, it will resort to a brute-force search of most (non-compressed) files in /var/log.

FILES

	   /proc/net/*
	   /var/log/*
	   /etc/ipsec.conf
	   /etc/ipsec.secrets

HISTORY

       Written for the Linux FreeS/WAN project <http://www.freeswan.org> by Henry Spencer.

BUGS

       Barf uses heuristics to try to pick relevant material out of the logs, and relevant messages which are not labelled with any of the tags
       that barf looks for will be lost. We think we've eliminated the last such case, but one never knows...

       Finding updown scripts (so they can be included in output) is, in general, difficult.  Barf uses a very simple heuristic that is easily
       fooled.

       The brute-force search for the right log files can get expensive on systems with a lot of clutter in /var/log.

AUTHOR

       Paul Wouters
	   placeholder to suppress warning

libreswan							    12/16/2012							     IPSEC_BARF(8)

Check Out this Related Man Page

DOVEADM-LOG(1)							      Dovecot							    DOVEADM-LOG(1)

NAME

       doveadm-log - Locate, test or reopen Dovecot's log files

SYNOPSIS

       doveadm [-Dv] log errors
       doveadm [-Dv] log find [directory]
       doveadm [-Dv] log reopen
       doveadm [-Dv] log test

DESCRIPTION

       The  doveadm  log commands are used to locate and reopen the log files of dovecot(1).  It's also possible to test the configured targets of
       the *log_path settings.

OPTIONS

       Global doveadm(1) options:

       -D     Enables verbosity and debug messages.

       -v     Enables verbosity, including progress counter.

COMMANDS

   log errors
       doveadm log errors

       The log errors command is used to show the last	- up to 1,000 - errors and warnings.  If no output is generated, no errors  have  occurred
       since the last start.

   log find
       doveadm log find [directory]

       The  log  find  command	is used to show the location of the log files, to which dovecot(1) sends its log messages.  If dovecot(1) logs its
       messages through syslogd(8) and doveadm(1) could not find any log files, you can specify the directory where your syslogd  writes  its  log
       files.

   log reopen
       doveadm log reopen

       This command causes doveadm to reopen all log files, configured in the log_path, info_log_path and debug_log_path settings.  These settings
       are configured in /etc/dovecot/conf.d/10-logging.conf.
       This is for example useful after manually rotating the log files.

   log test
       doveadm log test

       This command causes doveadm to write the message "This is Dovecot's priority log (timestamp)" to the configured log files.  The used prior-
       ities are: debug, info, warning, error and fatal.

EXAMPLE

       This example shows how to locate the log files used by dovecot(1).

       doveadm log find
       Looking for log files from /var/log
       Debug: /var/log/dovecot.debug
       Info: /var/log/mail.log
       Warning: /var/log/mail.log
       Error: /var/log/mail.log
       Fatal: /var/log/mail.log

REPORTING BUGS

       Report  bugs,  including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>.	Information about reporting bugs is avail-
       able at: http://dovecot.org/bugreport.html

SEE ALSO

       doveadm(1)

Dovecot v2.1							    2012-02-22							    DOVEADM-LOG(1)

Linux and UNIX Man Pages

ipsec_barf(8) [centos man page]

Check Out this Related Man Page