Salut Jerome -
Radiator already has this support in the form of the PacketTrace parameter and the <Monitor> clause.
Our companion product Radar uses both features to allow to connect to a running Radiator instance and do lots of interesting things.
www.open.com.au/radar
See the relevant sections of the Radiator 3.6 reference manual ("doc/ref.html").
PS - the Monitor clause can be accessed via telnet also.
regards
Hugh
On Tuesday, Sep 9, 2003, at 22:18 Australia/Melbourne, Jerome Fleury wrote:
Hi,
I'd like to suggest a new radiator feature:
since we have very busy servers (more than 30 req/s), we would like sometimes to have traces
for a specific login/client/whatever. I'd like the possibility to add some Trace option that
would match some value, so that the logging occurs only if the value matches, instead of
logging everything by default
Hope that's clear enough :)
-- Jerome Fleury === 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, 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.
