Hi Craig -
Any combination of Log clauses will all log the same information, just to different places.
Handlers are evaluated after Realms, but I find it quite confusing having both in the same configuration file.
I quite often use two (or even more) instances of Radiator if I have complex processing (and logging) requirements.
regards
Hugh
On Monday, Jul 7, 2003, at 05:37 Australia/Melbourne, Craig Gittens wrote:
Ok. So I have my <log sql> as the very last item in the entire config and
not nested in the realm. If I do a handler does it still get logged? I think
it would but I have combed the Ref guide and I can't find the behaviour
tracing. So is there a way within that handler to tell it not to log to the
global <log sql> clause? And a handler is the next step after a realm right?
so if it matched a username "test" in the default realm would it still not
be logged?
The thing is after looking at this is that I should really be using <AuthLog
SQL> for Authentication. I will make the changes but what about the question
above?
Thanks,
Craig.
-----Original Message----- From: Hugh Irvine [mailto:[EMAIL PROTECTED] Sent: Friday, July 04, 2003 8:05 PM To: Craig Gittens Cc: Radiator Subject: Re: (RADIATOR) insert <log sql>
Hello Craig -
I generally find it easier to use Handlers for this sort of thing and process special usernames like "TEST" seperately:
<Handler User-Name = TEST> ..... </Handler>
.....
regards
Hugh
On Saturday, Jul 5, 2003, at 09:09 Australia/Melbourne, Craig Gittens wrote:
Hey guys,
Is there a way to exempt certain usernames from entering the sql log? I want to insert if username != TEST.
Thanks,
Craig
=== 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.
NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?
-- 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.
NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?
-- 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 [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
