We're in the process of switching to Radiator 2.13.1 from an ugly mix of
Merit, Cistron, and Ascend Access Control. It's looking good so far, but
I've run into a bit of a snag. I'm trying to specify what gets written
into the accounting files with AcctLogFileFormat statement, but I'm not
getting the results the reference manual implies I should.
Here's a brief snippet of an accounting record with no
AcctLogFileFormat:
Thu Jun 17 17:42:05 1999
User-Name = "fred@joe"
NAS-IP-Address = 192.168.10.11
NAS-Port = 51
NAS-Port-Type = Async
(long list of other attributes follows)
As a test, I decided to see if I could specify an AcctLogFileFormat
clause that would result in the same detail file format. So I added the
following to a test realm:
AcctLogFileFormat %{User-Name} %{NAS-IP-Address} %{NAS-Port} etc.
which is similar to the example in the ref manual (section 6.12.5). But
when I reloaded and ran a radpwtst, I ended up with the following:
fred@joe 192.168.10.11 Async Start 00001234
i.e., no datestamp at the start, no "attribute = " in front of the
values, and no newlines.
Any ideas regarding what I'm missing?
I'm doing this because our billing guy noticed that when Radiator
handles accounting, we end up with a "timestamp" attribute that's not
recorded when AAC does the accounting. His software won't understand the
extra attribute. He could change the software, but I'd like to get this
AcctLogFileFormat working so we can leave out attributes we decide not to
use in the future. If anyone's got any ideas on how to simply leave out
one or more attributes without a AcctLogFileFormat statement, I'd love to
hear them.
Ian Quorn
UNIX mook -- IWBC
"Living in a pretend world of happiness
My painted face melts as I recede
Into my own reality - into my hole"
-Solitude Aeturnus, "Never"
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
