Re: [RADIATOR] AuthLog SYSLOG - LogOpt PID

2014-02-24 Thread Kurt Bauer
Hello Heikki, Heikki Vatiainen mailto:h...@open.com.au 23. Februar 2014 22:42 On 02/21/2014 05:58 PM, Kurt Bauer wrote: Too easily find the logs from various servers apart I added a custom LogIdent parameter per Server, which works as expected. The problem now is, that Radiator appends

[RADIATOR] AuthLog SYSLOG - LogOpt PID

2014-02-21 Thread Kurt Bauer
to the LogIdent, which means, that the central tool identifies a new source whenever radiator is restarted, as the LogIdent as a whole changes. Is there away to omit the pid? I tried with just leaving LogOpt empty, which apparently doesn't work. Any help would be highly appreciated, best regards, Kurt -- Kurt

Re: [RADIATOR] Radiator Debian Wheezy = memory problem?

2013-07-04 Thread Kurt Bauer
/radiator/2013-June/019148.html We are currently integrating those changes to AuthRADSEC and in meantime I would advice not to use UseStatusServerForFailureDetect in AuthBy RADSEC. Best Regards, Sami On 06/19/2013 12:04 PM, Kurt Bauer wrote: Hi, since upgrading one of our radius-servers

[RADIATOR] Radiator Debian Wheezy = memory problem?

2013-06-19 Thread Kurt Bauer
plus latest patches Perl v5.14.2 (as packaged in Wheezy) Any similar experiences or hints why this could be? Restarting Radiator every few days rectifies the situation but is not the way we want to run the service ;-) Thanks for your help, best regards, Kurt -- Kurt

[RADIATOR] AuthByLDAP2 + AuthAttrDef and AuthByFILE

2012-01-20 Thread Kurt Bauer
and it isn't intended to work that way or am I missing smth. in my configuration? Thanks a lot for your help, best regards, Kurt -- Kurt Bauer kurt.ba...@univie.ac.at Vienna University Computer Center - ACOnet - VIX Universitaetsstrasse 7, A-1010 Vienna, Austria, Europe Tel: ++43 1 4277 - 14070