Alan DeKok <[EMAIL PROTECTED]> said:
> Dave Weis <[EMAIL PROTECTED]> wrote:
> > which is what I used for the layout. It looks the same in db_mysql.sql
also.
> >
> > Is it position sensitive or does it use column names?
>
> Hmm... The queries in SQL.conf select "id, username, attribute,
> valu
Dave Weis <[EMAIL PROTECTED]> wrote:
> which is what I used for the layout. It looks the same in db_mysql.sql also.
>
> Is it position sensitive or does it use column names?
Hmm... The queries in SQL.conf select "id, username, attribute,
value, op". So it should work, unless you edited the que
Alan DeKok wrote:
Dave Weis <[EMAIL PROTECTED]> wrote:
The other reply items come from radgroupreply. When I run radiusd -X I see
this in the logs:
modcall[post-auth]: module "sql" returns ok for request 0
modcall: group post-auth returns ok for request 0
Sending Access-Accept of id 59 to 127.0.
Dave Weis <[EMAIL PROTECTED]> wrote:
> The other reply items come from radgroupreply. When I run radiusd -X I see
> this in the logs:
>modcall[post-auth]: module "sql" returns ok for request 0
> modcall: group post-auth returns ok for request 0
> Sending Access-Accept of id 59 to 127.0.0.1:572
AIL PROTECTED]>
To:
Sent: Monday, May 09, 2005 6:58 AM
Subject: postgresql problem/question
I'm trying to use postgresql to store my radius data. I have most of it
working except for a stored procedure to return the static
routing/addressing information for a login. It tries to work
I'm trying to use postgresql to store my radius data. I have most of it
working except for a stored procedure to return the static
routing/addressing information for a login. It tries to work but I don't
get the correct output in radtest.
select * from generate_radreply('[EMAIL PROTECTED]');
6 matches
Mail list logo