(RADIATOR) Authlog

[Hugh Irvine]

Hello Todd -

Keep in mind that there are different things happening with what is output 
from Radiator. Standard error, debug, info messages and so on (controlled by 
the Trace setting) go to the LogFile or <Log SQL> clause or whatever. The 
<AuthLog ...> is only used for authentication logging. And the accounting 
records go to the AcctLogFileName or <AuthBy SQL> or whatever.

So the first thing to do is make sure that you are sending the correct thing.

Note that there is no such thing as an <AuthLog EMERALD> clause, but you 
should be able to use an <AuthLog SQL> to point to the EMERALD database.

You will also have to make sure that there is a suitable table for you to use.

regards

Hugh


On Thursday 25 October 2001 03:50, Todd Dokey wrote:
> Is it okay to use this:
>
> <AuthLog EMERALD>
> (stock Emerald log stuff)
> </AuthLog>
>
> To push errors into the Emerald Radlogs table?
>
> Then just assign the error logging to it?
>
> I am having trouble getting it to work.
>
> Ideas?
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.