[RADIATOR] Dedicated debug/trace log for specific AuthBys and Handlers

[Hugh Irvine]

Hello Christian -

The way to do this is to define your Log clauses inside an AuthBy GROUP at the top of your configuration file.

Ie.

# define Log clauses for use elsewhere without them being global loggers

<AuthBy GROUP>

	<Log ….>
		Identifier Something
		…..
	</Log>

	<Log …..>
		Identifier Whatever
		…..
	</Log>

	…..

</AuthBy>


Then use the identifiers later.

	…..

	Log Something

	…..


btw - you can also use "Include …." directives to better organise your configuration file(s)

hope that helps

regards

Hugh


> On 12 Jan 2019, at 02:51, Christian Meutes <christian at errxtx.net> wrote:
> 
> Hello,
> 
> is it possible to turn trace logging for just individual Handlers or AuthBys on, for debugging purposes but without placing "<Log FILE>" clauses into all of them? It would be nice to have a centralized .cfg file containing "<Log FILE>" clauses and Handlers/AuthBys would just point to their identifiers by "Log foobar" or similar.
> 
> Any idea how to structure this ideally?
> 
> Thanks & Cheers
> -- 
> Christian
> _______________________________________________
> radiator mailing list
> radiator at lists.open.com.au
> https://lists.open.com.au/mailman/listinfo/radiator


--

Hugh Irvine
hugh at open.com.au

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER, SIM, etc. 
Full source on Unix, Linux, Windows, macOS, Solaris, VMS, NetWare etc.