(RADIATOR) strange authlog behavior (bug?)

Sam Nilsson sam at enabledsites.com
Mon Feb 11 17:25:03 CST 2002


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.


More information about the radiator mailing list