Guilherme Thanks I have committed a patch. Sorry about that. This is one of the reasons why I normally dont keep the different sql dialect files in sync without significant testing.. There are just too many differences. Unfortunately this causes them to gradually get out of sync over time. If you see any other issues, please let me know and I will fix them Regards Peter On Tue 18 Sep 2007, Guilherme Franco wrote:
Hello,
Just to note that oraclesql.conf (in 1.1.7) is wrong about the gigawords. The syntax for using bitwise operators is different in oracle and for such needs, you must use the BITAND function and its variants.
But instead of doing bit shifts, I did this to solve it:
AcctInputOctets = '%{Acct-Input-Octets}' + ('%{Acct-Input-Gigawords}' * 4294967296), AcctOutputOctets = '%{Acct-Output-Octets}' + ('%{Acct-Output-Gigawords}' * 4294967296)
Guilherme Franco
On 9/14/07, Guilherme Franco <guilhermefranco@gmail.com> wrote:
Hi Mr. DeKok,
Ok, I've just asked it because of: http://wiki.freeradius.org/index.php/FAQ#Why_do_Acct-Input-Octets_and_Ac ct-Output-Octets_wrap_at_4_GB.3F (which says that it should work in older versions)
Also, the rlm_sql_log module version is the same in 1.1.7 as in 1.1.4 (v 1.3.2.2 2005/12/12).
Thank you.
Guilherme Franco
On 9/14/07, Alan DeKok <aland@deployingradius.com> wrote:
Guilherme Franco wrote:
Hello,
I'm using rlm_sql_log in freeradius 1.1.4.
In order to correctly work with acct-input/ output gigawords,
Upgrade to 1.1.7.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Peter Nixon http://peternixon.net/