10 Jun
2015
10 Jun
'15
9:51 a.m.
On Jun 10, 2015, at 1:21 AM, d tbsky <tbskyd@gmail.com> wrote:
after checking the detail of "queries.conf". I found it is actually a bad thing. when updating it really only use "acctsessionid + username + nasipaddress" to locate existing record without other constraint. so in my case, even I create a unique 'acctuniqid', all the existing records with the same "acctsessionid" will be updated at once. maybe the whole update process in queries.conf should be modified to use "acctuniqid" when locate existing record?
Hmm... in v3.0.x in git, the queries do use Acct-Unique-Session-Id. Which version are you using? Which queries don't use Acct-Unique-Session-Id? Alan DeKok.