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@warner.fm> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: FreeRadius users mailing list <freeradius-users@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