Currently, a typical detail entry from Radiator looks like:
Thu Dec 16 16:30:33 1999
User-Name = "dave"
Service-Type = Framed-User
NAS-IP-Address = 253.63.154.1
NAS-Port = 1234
NAS-Port-Type = Async
Acct-Session-Id = "00001234"
Acct-Status-Type = Stop
Acct-Delay-Time = 0
Acct-Session-Time = 1000
Acct-Input-Octets = 20000
Acct-Output-Octets = 30000
Timestamp = 945379833
However, our current Sql Server database is set up relationally, so that in
the column for ServiceType, we have numerical entries rather than text
entries like "Framed-User". The same applies to NAS-Port-Type,
Acct-Status-Type, Acct-Authentic, User-Service, Login-Service,
Framed-Protocol, and others. The "dictionary" in our database consists of
Emerald-style tables, RadAttributes and RadValues, to do the appropriate
lookups.
Now, we are using a custom accounting interface which will read the detail
text files in standard Radiator format, parse them, and INSERT them into
this table. I've tried several database tricks to try to coerce the detail
data into our table, such as INSERT with JOIN, Views, etc, to no avail.
So.......
I'm assuming Radiator natively receives this data in the numeric form
rather than the text form. So, what would fix the problem, I think, would
be if I could tell Radiator to stop looking up values in the dictionary,
and instead just log the raw numeric values in the detail file.
Is this possible?
Dave
NetCarrier
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
