On 04/01/2014 02:59 PM, Hartmaier Alexander wrote: > I think extending LogFormat is the right way to go because one might > want to log to a file or database in json or yaml as well. > What I still haven't figured out is a config format. > Enabling to pass a Perl sub to LogFormat would be the most flexible > option but not the most user friendly. > > Ideas?
Wouldn't subclassing Log FILE work. Or maybe subclassing LogGeneric directly? I'd think keeping Log FILE as simple and straight forward would be a good goal since sometimes (Trace 4) a lot of traffic will pass through it. Thanks, Heikki -- Heikki Vatiainen <h...@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 etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
