Subversion Repositories configs

Rev

Rev 4 | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
4 - 1
# -*- text -*-
2
#
34 - 3
#  $Id: a57741ac3fa5f884ed64d896da3807af5d2a6b99 $
4 - 4
 
5
#
6
#  The "linelog" module will log one line of text to a file.
7
#  Both the filename and the line of text are dynamically expanded.
8
#
9
#  We STRONGLY suggest that you do not use data from the
10
#  packet as part of the filename.
11
#
12
linelog {
13
	#
14
	#  The file where the logs will go.
15
	#
16
	#  If the filename is "syslog", then the log messages will
17
	#  go to syslog.
18
	filename = ${logdir}/linelog
19
 
20
	#
21
	#  The Unix-style permissions on the log file.
22
	#
23
	#  Depending on format string, the log file may contain secret or
24
	#  private information about users.  Keep the file permissions as
25
	#  restrictive as possible.
26
	permissions = 0600
27
 
28
	#
34 - 29
	# The Unix group of the log file.
30
	#
31
	# The user that freeradius runs as must be in the specified
32
	# group, otherwise it will not be possible to set the group.
33
	#
34
	# group = freerad
35
 
36
	#
37
	# If logging via syslog, the facility can be set here. Otherwise
38
	# the syslog_facility option in radiusd.conf will be used.
39
	#
40
	# syslog_facility = daemon
41
 
42
	#
4 - 43
	#  The default format string.
44
	format = "This is a log message for %{User-Name}"
45
 
46
	#
47
	#  This next line can be omitted.  If it is omitted, then
48
	#  the log message is static, and is always given by "format",
49
	#  above.
50
	#
51
	#  If it is defined, then the string is dynamically expanded,
52
	#  and the result is used to find another configuration entry
53
	#  here, with the given name.  That name is then used as the
54
	#  format string.
55
	#
56
	#  If the configuration entry cannot be found, then no log
57
	#  message is printed.
58
	#
59
	#  i.e. You can have many log messages in one "linelog" module.
60
	#  If this two-step expansion did not exist, you would have
61
	#  needed to configure one "linelog" module for each log message.
62
 
63
	#
64
	#  Reference the Packet-Type (Access-Request, etc.)  If it doesn't
65
	#  exist, reference the "format" entry, above.
66
	reference = "%{%{Packet-Type}:-format}"
67
 
68
	#
69
	#  Followed by a series of log messages.
70
	Access-Request = "Requested access: %{User-Name}"
71
	Access-Reject = "Rejected access: %{User-Name}"
72
	Access-Challenge = "Sent challenge: %{User-Name}"
73
 
74
	#
75
	#  The log messages can be grouped into sections and
76
        #  sub-sections, too.  The "reference" item needs to have a "."
77
	#  for every section.  e.g. reference = foo.bar will reference
78
	#  the "foo" section, "bar" configuration item.
79
	#
80
 
81
	#
82
	#  Used if:	reference = "foo.bar".
83
	foo {
84
	    bar = "Example log.  Please ignore"
85
	}
86
 
87
	#
88
	#  Another example:
89
	#      reference = "Accounting-Request.%{%{Acct-Status-Type}:-unknown}"
90
	#
91
	Accounting-Request {
92
		Start = "Connect: [%{User-Name}] (did %{Called-Station-Id} cli %{Calling-Station-Id} port %{NAS-Port} ip %{Framed-IP-Address})"
93
		Stop = "Disconnect: [%{User-Name}] (did %{Called-Station-Id} cli %{Calling-Station-Id} port %{NAS-Port} ip %{Framed-IP-Address}) %{Acct-Session-Time} seconds"
94
 
95
		#  Don't log anything for these packets.
96
		Alive = ""
97
 
98
		Accounting-On = "NAS %C (%{NAS-IP-Address}) just came online"
99
		Accounting-Off = "NAS %C (%{NAS-IP-Address}) just went offline"
100
 
101
		# don't log anything for other Acct-Status-Types.
102
		unknown = ""
103
	}
104
 
105
}