FYI, radreply items override radgroupreply. I have Idle-Timeout in
both radreply and radgroupreply and user's values override what is set
in groups.
Why is this processing order different for check items? It is quite
natural to set default values in group and override the defaults for
some users
It's to do with operators rather than tables. = will not replace
attribute value if one already exists. := will.
There is a case for blocking this in cases when same attribute has both
user and group sql entry. That would enable for user entries to take
preferance over group entries even when :=
Hi JT,
You can apply following patch to prevent group attributes with
operator := overwriting user attributes. Just commenting out the
overwritng code in valuepair.c
Regards,
Abraham
--- src/main/valuepair.c.orig 2008-09-17 16:57:25.0 +0530
+++ src/main/valuepair.c2008-09-17
Thanks Ivan for clarifying reply items query.
Jacob, Thanks for the patch. One question, will it break any other
functionality or modules to behave differnetly? I see this function is
being called from many places in the source tree.
Thanks,
JT
2008/9/17 Abraham Jacob [EMAIL PROTECTED]:
Hi JT,
Abraham Jacob wrote:
You can apply following patch to prevent group attributes with
operator := overwriting user attributes. Just commenting out the
overwritng code in valuepair.c
Or, change := to = in the group check table. Which also has the
benefit of *not* changing the behavior of :=
On Wed, Sep 17, 2008 at 5:20 PM, Alan DeKok [EMAIL PROTECTED] wrote:
Or, change := to = in the group check table. Which also has the
benefit of *not* changing the behavior of := for everything else in
the server.
I tried changing operator to '=' but sqlcounter fails with following message.
6 matches
Mail list logo
