(RADIATOR) strange authlog behavior (bug?)

[Hugh Irvine]

Hello Sam -

Can you send me a copy of your configuration file (no secrets) together with 
a trace 4 debug showing what happens in both cases? And what version of 
Radiator are you running and on what hardware/software platform?

thanks

Hugh


On Tue, 12 Feb 2002 10:25, Sam Nilsson wrote:
> We are using individual authlog clauses for our handlers.
> These look like this...
>
> <AuthLog FILE>
> Filename /path/to/logs/%R/%R_auth_%m%d%Y.log
> LogSuccess 1
> LogFailure 1
> </AuthLog>
>
> When we kill -HUP the radius process, the new handler that
> we've added begins working properly. However, the authlog
> doesn't get created or written to.
>
> After killing the process (not hupping it) and then starting radiator
> again, the authlog magically starts working.
>
> I may be missing something, but this appears to be a bug in the way
> radiator handles a HUP signal.
>
> Has anyone else seen this? Can anyone confirm or deny this?
>
> - Sam
>
> ===
> 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.