57 lines
1.2 KiB
Plaintext
57 lines
1.2 KiB
Plaintext
# You can use this to rotate the /var/log/radius/* files, simply copy
|
|
# it to /etc/logrotate.d/radiusd
|
|
|
|
# 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 {
|
|
monthly
|
|
rotate 4
|
|
nocreate
|
|
missingok
|
|
compress
|
|
su radiusd radiusd
|
|
}
|
|
|
|
/var/log/radius/checkrad.log {
|
|
monthly
|
|
rotate 4
|
|
create
|
|
missingok
|
|
compress
|
|
su radiusd radiusd
|
|
}
|
|
|
|
/var/log/radius/radius.log {
|
|
monthly
|
|
rotate 4
|
|
create
|
|
missingok
|
|
compress
|
|
su radiusd radiusd
|
|
postrotate
|
|
/usr/bin/systemctl reload-or-try-restart radiusd
|
|
endscript
|
|
}
|
|
|
|
/var/log/radius/radwtmp {
|
|
monthly
|
|
rotate 4
|
|
create
|
|
compress
|
|
missingok
|
|
su radiusd radiusd
|
|
}
|
|
/var/log/radius/sqltrace.sql {
|
|
monthly
|
|
rotate 4
|
|
create
|
|
compress
|
|
missingok
|
|
su radiusd radiusd
|
|
}
|