Dear all,
Can you give me an example of how to set the cache-size ?
This is my config for the counter.
counter daily {
filename = ${raddbdir}/db.daily
key = User-Name
count-attribute = Acct-Session-Time
reset = daily
counter-name = Daily-Session-Time
check-name = Max-Daily-Session
allowed-servicetype = Framed-User
cache-size = 5000
# The RADIUS request is normally cached internally for a short period
# of time, after the reply is sent to the NAS. The reply packet may be
# lost in the network, and the NAS will not see it. The NAS will then
# re-send the request, and the server will respond quickly with the
# cached reply.
#
# If this value is set too low, then duplicate requests from the NAS
# MAY NOT be detected, and will instead be handled as seperate requests.
#
# If this value is set too high, then the server will cache too many
# requests, and some new requests may get blocked. (See 'max_requests'.)
#
# Useful range of values: 2 to 10
#
cleanup_delay = 5
Regards
Angus
<<Email Disclaimer>>
This e-mail and its attachments, if any, are confidential and contain
information for an intended recipient. The Open University of Hong Kong (OUHK)
disclaims any liability for any loss or damage if this e-mail is received by
any person who is not the intended recipient. E-mail transmissions cannot be
guaranteed to be completely secure, error or virus free. No responsibility is
accepted by the OUHK for any loss or damage arising in any way from receipt or
use thereof. Arrangements or statements appearing to bind OUHK are not binding
upon OUHK unless made in accordance with OUHK's constitution and duly
authorised. OUHK staff are expressly prohibited from breaching applicable law,
infringing third party rights, making defamatory statements and committing
tortious acts by e-mail communications.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
