653d32
# You can use this to rotate the /var/log/radius/* files, simply copy
653d32
# it to /etc/logrotate.d/radiusd
653d32
653d32
# There are different detail-rotating strategies you can use.  One is
653d32
# to write to a single detail file per IP and use the rotate config
653d32
# below.  Another is to write to a daily detail file per IP with:
653d32
#     detailfile = ${radacctdir}/%{Client-IP-Address}/%Y%m%d-detail
653d32
# (or similar) in radiusd.conf, without rotation.  If you go with the
653d32
# second technique, you will need another cron job that removes old
653d32
# detail files.  You do not need to comment out the below for method #2.
653d32
/var/log/radius/radacct/*/detail {
653d32
	monthly
653d32
	rotate 4
653d32
	nocreate
653d32
	missingok
653d32
	compress
653d32
}
653d32
653d32
/var/log/radius/checkrad.log {
653d32
	monthly
653d32
	rotate 4
653d32
	create
653d32
	missingok
653d32
	compress
653d32
}
653d32
653d32
/var/log/radius/radius.log {
653d32
	monthly
653d32
	rotate 4
653d32
	create
653d32
	missingok
653d32
	compress
653d32
	postrotate
653d32
		/usr/bin/systemctl reload-or-try-restart radiusd
653d32
	endscript
653d32
}
653d32
653d32
/var/log/radius/radwtmp {
653d32
	monthly
653d32
	rotate 4
653d32
	create
653d32
	compress
653d32
	missingok
653d32
}
653d32
/var/log/radius/sqltrace.sql {
653d32
        monthly
653d32
        rotate 4
653d32
        create
653d32
        compress
653d32
        missingok
653d32
}