blob: 5ebfcf3295a813cf939e85a2ebe35c140597c052 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
#
# You can use this to rotate the /var/log/radius/* files, simply copy
# it to /etc/logrotate.d/radiusd
#
#
# The main server log
#
/var/log/radius/radius.log {
# Common options
dateext
maxage 365
rotate 99
missingok
compress
delaycompress
notifempty
su radiusd radiusd
copytruncate
}
#
# Session monitoring utilities and SQL log files (in order)
#
/var/log/radius/checkrad.log /var/log/radius/radwatch.log
/var/log/radius/sqllog.sql
{
# Common options
dateext
maxage 365
rotate 99
missingok
compress
delaycompress
notifempty
su radiusd radiusd
nocreate
size=+2048k
}
#
# There are different detail-rotating strategies you can use. One is
# to write to a single detail file per IP and use the rotate config
# below. Another is to write to a daily detail file per IP with:
#
# detailfile = ${radacctdir}/%{Client-IP-Address}/%Y%m%d-detail
#
# (or similar) in radiusd.conf, without rotation. If you go with the
# second technique, you will need another cron job that removes old
# detail files. You do not need to comment out the below for method #2.
#
/var/log/radius/radacct/*/detail {
# Common options
dateext
maxage 365
rotate 99
missingok
compress
delaycompress
notifempty
su radiusd radiusd
nocreate
}
|
