sslogger.conf

Langue: en

Version: February 2009 (fedora - 01/12/10)

Section: 5 (Format de fichier)

NAME

sslogger.conf - sslogger(5) configuration file

DESCRIPTION


      sslogger.conf  is a simple file containing  values to be read by 
      sslogger.  The syntax is simply as follows:


              # comment
              token=value


       Note that blank lines are ignored, no whitespace are permitted before
       the token, after the token, or before the value. Lines which begin with
       a # are considered  comments and ignored.

FILES

/etc/sslogger.d/sslogger.conf
Default Configuration File

EXAMPLE CONFIGURATION FILE

Configuration file /etc/sslogger.d/sslogger.conf:

# Log output of all commands, even non interactive (1 is true). Default 0
log_all_cmds=0

# Minimum Comment length in chars
#an entry of 0 will skip reason for asking for a shell
min_comment=10

# Maximum Comment Length in chars written to syslog
#Comment Length in the session log file is currently unlimited
max_comment=60

# To allow normal users replay access to log files they create, Set below to 1
allow_user_replay=1

# slogd server name or ip.
# If commented out or empty remote log collection is disabled
slogd_server=

#slogd service port
slogd_server_port=5556

#slogd auth type. Must match slogd server tls_authtype
# Current options are "x509" or "anon".
# Setting to x509 requires x509 tls certs
# to be generated and pushed to all clients. See the mkSlogCerts command
slogd_authtype=anon

# When using a slogd server, and a sslogger session is over, and logs are
# properly transferred to slogd server, delete the local log file.
# Setting to 1 will enable keeping of all local log file.
keep_local_logs=0

# Policy for when a connection to a slogd server is unavailable or
# unexpectedly terminated. If set to 1, sslogger will terminate if
# connection is broken to slogd server, and session will die if it
# cannot connect to the remote slogd server at start up.
# If set to 0, local logging will be used when we can not contact remote
# server or when a network connection to the slogd server is broken
require_remote_slogd=0

BUGS

If you feel you have found a bug in sslogger, please submit a bug report at http://sslogger.sourceforge.net

SUPPORT

Limited free support is available via the sslogger-users mailing list, see http://sslogger.sourceforge.net to subscribe or search the archives.

AUTHOR

Edward Brand <edbrand@brandint.com>

SEE ALSO

slog(8) sreplay(8) sslogger-slogd(8) mkSlogCerts(8) sudo(8), suders(8), su(2)