Thanks for the response. I don't really like the session-time out solution wouldn't this mean the users would get disconnected every 23 hours. And if they first connect during the middle of the day then this will cause problems. I was thinking of changing the accounting_update_query so that it would create a new record every 23:59's of running and then update the new record with new data. This would allow query's to be run on the existing database with out any major changes. I have been doing this manually by changing accounting_update_query_alt to accounting_update_query restarting radius waiting a few mins then changing it back. But I was looking for a more automated fix. This also has the added benefit of being able to run reports daily, weekly , monthly ,yearly for time and data. Can you see any problems with my suggestion? Also do you know when the accounting_update_query_alt is used over the accounting_update_query I may be able to use this to implement my fix. Thank you Andrew Paternoster -----Original Message----- From: freeradius-devel-bounces+andrew=gpk.net.au@lists.freeradius.org [mailto:freeradius-devel-bounces+andrew=gpk.net.au@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Tuesday, 10 February 2009 8:18 PM To: FreeRadius developers mailing list Subject: Re: FW: FreeRadius Data Accounting Andrew Paternoster wrote:
I was wondering if I could get some insight to how people are doing daily data accounting for users that stay connected for days. E.g. Adsl's or dial ups. The problem seems to be that the records in radacct only get a time stamp on a stop or a start. And the session time is updated at every interval.
Could I find out if others have managed to get around this problem and how.
(1) They set Session-Timeout so that the users don't stay on for days. (2) they write scripts to collate the information. It should be pretty easy to write a select statement that grabs all records which don't have a STOP. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html