1sslogger.conf(5) User Manuals sslogger.conf(5)
2
3
4
6 sslogger.conf - sslogger(5) configuration file
7
9 sslogger.conf is a simple file containing values to be read by
10 sslogger. The syntax is simply as follows:
11
12 # comment
13 token=value
14
15 Note that blank lines are ignored, no whitespace are permitted
16 before
17 the token, after the token, or before the value. Lines which
18 begin with
19 a # are considered comments and ignored.
20
22 /etc/sslogger.d/sslogger.conf
23 Default Configuration File
24
26 Configuration file /etc/sslogger.d/sslogger.conf:
27 # Log output of all commands, even non interactive (1 is true).
28 Default 0
29 log_all_cmds=0
30
31
32 # Minimum Comment length in chars
33 #an entry of 0 will skip reason for asking for a shell
34 min_comment=10
35
36
37 # Maximum Comment Length in chars written to syslog
38 #Comment Length in the session log file is currently unlimited
39 max_comment=60
40
41
42 # To allow normal users replay access to log files they create,
43 Set below to 1
44 allow_user_replay=1
45
46
47 # slogd server name or ip.
48 # If commented out or empty remote log collection is disabled
49 slogd_server=
50
51
52 #slogd service port
53 slogd_server_port=5556
54
55
56 #slogd auth type. Must match slogd server tls_authtype
57 # Current options are "x509" or "anon".
58 # Setting to x509 requires x509 tls certs
59 # to be generated and pushed to all clients. See the mkSlogCerts
60 command
61 slogd_authtype=anon
62
63
64 # When using a slogd server, and a sslogger session is over, and
65 logs are
66 # properly transferred to slogd server, delete the local log
67 file.
68 # Setting to 1 will enable keeping of all local log file.
69 keep_local_logs=0
70
71
72 # Policy for when a connection to a slogd server is unavailable
73 or
74 # unexpectedly terminated. If set to 1, sslogger will terminate
75 if
76 # connection is broken to slogd server, and session will die if
77 it
78 # cannot connect to the remote slogd server at start up.
79 # If set to 0, local logging will be used when we can not con‐
80 tact remote
81 # server or when a network connection to the slogd server is
82 broken
83 require_remote_slogd=0
84
85
86
88 If you feel you have found a bug in sslogger, please submit a bug
89 report at http://sslogger.sourceforge.net
90
92 Limited free support is available via the sslogger-users mailing list,
93 see http://sslogger.sourceforge.net to subscribe or search the ar‐
94 chives.
95
97 Edward Brand <edbrand@brandint.com>
98
100 slog(8) sreplay(8) sslogger-slogd(8) mkSlogCerts(8) sudo(8), suders(8),
101 su(2)
102
103
104
105Linux February 2009 sslogger.conf(5)