Just looking at some of my records, would I be right in
observing that the default *sql.conf files don't account
for Acct-Output-Gigawords and Acct-Input-Gigawords?
In the process of repairing damage done to my Calling-Station-ID
and NASPortId fields by too-short field lengths, I noticed
that several of my customers had managed to get a 1 in their
Acct-Output-Gigawords, but that hadn't been taken into account
in the mysql table...
If I'm right and it's not being accounted for, is there any
reason I wouldn't want to modify the query to be
SET AcctInputOctets = %{Acct-Input-Octets} +
(%{Acct-Input-Gigawords} * 4294967296)
I can't use rlm_expr here since rlm_expr only deals with
values up to 32-bits...
Otherwise I'll add the Gigaword columns as extra columns.
Either way, I'll submit a patch for support one way or the
other to the -devel list for discussion, unless someone
points out why it's not a good idea.
--
=========================================================
Paul "TBBle" Hampson
Bubblesworth Pty Ltd (ABN: 51 095 284 361)
[EMAIL PROTECTED]
This is a one line proof...if we start
sufficiently far to the left.
-- Cambridge University Math Department
---------------------------------------------------------
Random signature generator 3.0 by Paul "TBBle" Hampson
=========================================================
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
