(RADIATOR) rewriting LOG::INFO

[Hugh Irvine]

Hello SHAN -

It is not possible to avoid the second log message (without altering 
the Radiator code).

regards

Hugh


On 7 May 2004, at 21:18, S H A N wrote:

> hi,
> 	i am using the attached hook meant to do Single Session.
>
> 	if the user tries to do a 2nd concurrent session the hook will reject 
> the login and "MaxSession Exceeded" will be written out in logs but 
> unfortunately in the log the following is being shown up:
>
> 	-- snippet from logfile --
>
> 	Fri May  7 18:30:08 2004: INFO: Access rejected for shanali: 
> MaxSession Exceeded
> 	Fri May  7 18:30:08 2004: INFO: Access rejected for shanali:
>
> 	i would like to find out how to avoid printing in the second 
> occurrence of INFO message?
>
> 	thanks & warm regards
>
> S H A N
> <uniqSession.pl>

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.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.

--
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.