Re: [RADIATOR] AuthLog SYSLOG - LogOpt PID
On 02/24/2014 11:23 AM, Kurt Bauer wrote:
Yes I tried, but it didn't make any difference. Seems 'pid' is always used.
I manually changed $self-{LogOpt} in AuthLogSYSLOG.pm and LogSYSLOG.pm
from 'pid' to 'cons', which does the 'trick', but is a dirty hack of
course.
I did some testing with Ubuntu 12.04 and Radiator 4.12.1 but had
different results. Setting LogOpt to 'cons' changed the format so that
the PID was not printed anymore. Also, an empty value, that is just
LogOpt with no value, worked to remove the PID.
As a more permanent solution, I think an empty value can be allowed by
Radiator for LogOpt to turn off any non-default options.
As mentioned above, it worked for me. This might be caused by different
Sys-Syslog versions. Ubuntu 12.04 uses Sys-Syslog version 0.27.
That would be best I think. Having the hostname as LogIdent and no
LogOpt (even the trailing colon may be omitted) would be the most
generic approach and the waz standard remote syslog works.
The trailing colon is added by Sys-Syslog. Radiator does not add it, so
you would need to change Sys-Syslog to get rid of it.
In summary: I was able to change LogOpt to drop the PID variable. Empty
value for LogOpt worked as did setting the value to cons. I'm not sure
if this difference comes from Radiator or Sys-Syslog version.
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
Re: [RADIATOR] AuthLog SYSLOG - LogOpt PID
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 the pid in square brackets 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?
Hello Kurt,
have you tried using for example, cons as LogOpt option value? It
appears this option is ignored by the recent Sys::Syslog modules.
Yes I tried, but it didn't make any difference. Seems 'pid' is always used.
I manually changed $self-{LogOpt} in AuthLogSYSLOG.pm and LogSYSLOG.pm
from 'pid' to 'cons', which does the 'trick', but is a dirty hack of
course.
I tried with just leaving LogOpt empty, which apparently doesn't work.
As a more permanent solution, I think an empty value can be allowed by
Radiator for LogOpt to turn off any non-default options.
That would be best I think. Having the hostname as LogIdent and no
LogOpt (even the trailing colon may be omitted) would be the most
generic approach and the waz standard remote syslog works.
Thanks a lot,
best regards,
Kurt
Thanks,
Heikki
Kurt Bauer mailto:kurt.ba...@univie.ac.at
21. Februar 2014 16:58
Hi,
I recently tried to integrate Radiator syslog messages into our central
logging tool.
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 the pid in square brackets 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
smime.p7s
Description: S/MIME Cryptographic Signature
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] AuthLog SYSLOG - LogOpt PID
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 the pid in square brackets 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? Hello Kurt, have you tried using for example, cons as LogOpt option value? It appears this option is ignored by the recent Sys::Syslog modules. I tried with just leaving LogOpt empty, which apparently doesn't work. As a more permanent solution, I think an empty value can be allowed by Radiator for LogOpt to turn off any non-default options. 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
