problem with rlm_counter module when reset option is set to never

[Ahmed Nifaz Faizabadi]

On Tue, May 26, 2009 at 7:19 PM, Alan DeKok <aland at deployingradius.com> wrote:
> Ahmed Nifaz Faizabadi wrote:
> ....
>>>> counter daily {
>>>>        counter-name = Max-All-Session-Time
>>>>        check-name = Max-All-Session
>>>>        key = User-Name
>>>>        reset = never
> ...
>>>> I am observing that the user accounting record is not deleted from
>>>> rlm_counter module once the user has used his allocated time.
> ...
>>    This would increase the accounting file size indefenitely and cause
>> some other problems as the user records are not at all being deleted.
>
>  See the configuration: "reset = never" means "never reset".  Which
> means "don't reset".
>
    I agree with your explanation :). But it's a problem.

>>   I tried that but that accounting file is in binary or some other
>> encrypted format. Will you please let me know about how to delete that
>> accounting record or how to convert that to simple text file ( which
>> would make easy deleting expired records) .
>
>  It's just a DBM file.  See the "rad_counter.pl" file in the source
> tree.  It shows how to edit the file.
>
   I tried deleting using rad_counter.pl, but it doesn't work as gdbm
does not allow more than one writer to that file.

   I guess I need to patch up freeradius where a delete user message
(my own defnied) is sent to freeradius from NAS. On recieveing this
freeradius would just go and delete the users mentioned in that
message. I would be introducing a new listener for that purpose.
will that be ok ?

  I have other option of shutting down freeradius and then delete
users using rad_counter.pl, but that would lead to unavailability of
service for some time.

regards
Ahmed Nifaz