>
> > So, as you can see from my comments, the Session-Timeout attribute isn't
> > present in the radius response debug from the first login. The second
> time
> > when it appears, it is caluculated correctly. For now I think that I
> have an
> > issue with FR, so I don't go further to my chillispo
On Fri, Jun 29, 2012 at 2:58 PM, Andrei Petru Mura wrote:
> Fri Jun 29 10:20:06 2012 : Info: [hourlycounter] expand: %{sql:SELECT
> SUM(AcctSessionTime - GREATER((1340953200 -
> AcctStartTime::ABSTIME::INT4), 0)) FROM radacct WHERE
> UserName='test1' AND
1. So, in fact I optimized my counter.conf files following the wiki page
related to Rlm_sqlcounter module (http://wiki.freeradius.org/Rlm_sqlcounter)
2. I also followed the radius debug trace, but being relatively new to FR,
I neglect to put it in my post. I beg your pardon!
Following your thought
On Thu, Jun 28, 2012 at 7:34 PM, Andrei Petru Mura wrote:
> id | username | attribute | op | value
>
> -++++
> 167 | test1 | Password | := | test1
> 168 | test1
Andrei Petru Mura wrote:
> Now in my database. I have in "radcheck" table two rows:
>
>id | username | attribute| op | value
>
> -++++
> 167 | test1 | Password
I'm running FreeRADIUS in conjunction with PostgreSQL 9.1. Snippet from
radiusd.conf:
modules {
...
$INCLUDE sql/postgresql/counter.conf
...
}
in my sql/postgresql/counter.conf, I have the following:
sqlcounter dailycounter {
counter-name = Daily-Session-Time
check-name
6 matches
Mail list logo