Hello,
>From what I can understand, the timestamp used in AuthSQL for accounting is
the Timestamp attribute that is created in the request packet by the current
time minus Acct-Delay-Time.
However, when I have one Radiator proxying to another, the 2nd Radiator ends
up with 2 Timestamp different attributes. It isn't clear to me which one will
be used by the 2nd Radiator. I see get_attr in the code being called for this
value but wouldn't this just return the first (incorrect) Timestamp value?
Would it be better for me to depend on a database function for the timestamp?
For example, with an insert statement similar to:
..., now() - 0%{Acct-Delay-Time}, ...
Viraj.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
