Fwd: Specifying sql instance to use for huntgroup group lookup

[Doug Warner]

I found that all SQL instances would register themselves to handle the
Sql-Group processing even if they couldn't.  I've attached a patch that only
attaches the instance to process Sql-Group if group_membership_list is set.
I'm not sure if this is the best method for doing this or whether a new
variable is called for, but thought I would share this regardless.

-Doug


-------- Original Message --------
Subject: Specifying sql instance to use for huntgroup group lookup
Date: Mon, 21 Jun 2010 15:52:00 -0400
From: Doug Warner <doug at warner.fm>
Reply-To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>

I am specifying an Sql-Group required for one of my huntgroups and am finding
that when looking up the group info from my database that the wrong sql
instance is being used.  I have an "sql_read" instance that's specified to be
used in my authorize section, but when the Sql-Group is evaluated for the
huntgroup my "sql_write" sql instance is used instead.

Is there a way to specify which sql instance should be used in this situation?

-Doug



-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Attached Message Part
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20100622/8ab4b38f/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freeradius-2.1.9-sql-group-process.patch
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20100622/8ab4b38f/attachment-0001.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20100622/8ab4b38f/attachment.pgp>