HI!
I'm wondering why there are two log lines for listing the search parameters for a single search operation:
SRCH base="dc=ae-dir,dc=example,dc=org" scope=2 deref=0 filter="(objectClass=aePerson)"
SRCH attr=cn givenName sn mail aeStatus
Is there any rationale for that? Wouldn't it be better to also list attr= along with the other search parameters? The attributes could also be listed as comma-separated list, so parsing with space as separator would be easy.
I'm asking for a rather *small* change. I deliberately do not want to start a let's-fix-all-the-log-issues discussion.
Ciao, Michael.
Michael Ströder wrote:
HI!
I'm wondering why there are two log lines for listing the search parameters for a single search operation:
SRCH base="dc=ae-dir,dc=example,dc=org" scope=2 deref=0 filter="(objectClass=aePerson)"
SRCH attr=cn givenName sn mail aeStatus
Is there any rationale for that?
Because any of DN, filter, or attrs could be too long for a single syslog message. On many systems the limit was 1024 characters; using a single log message resulted in too many truncated messages.
On 2/11/20 1:48 PM, Howard Chu wrote:
Michael Ströder wrote:
I'm wondering why there are two log lines for listing the search parameters for a single search operation:
SRCH base="dc=ae-dir,dc=example,dc=org" scope=2 deref=0 filter="(objectClass=aePerson)"
SRCH attr=cn givenName sn mail aeStatus
Is there any rationale for that?
Because any of DN, filter, or attrs could be too long for a single syslog message. On many systems the limit was 1024 characters; using a single log message resulted in too many truncated messages.
Oh, I see [1].
Even in 2009 only a SHOULD for 2048 octets was defined while the MUST minimum was _lowered_ to 480 [2].
Ciao, Michael.
--On Tuesday, February 11, 2020 3:22 PM +0100 Michael Ströder michael@stroeder.com wrote:
Oh, I see [1].
Even in 2009 only a SHOULD for 2048 octets was defined while the MUST minimum was _lowered_ to 480 [2].
Seems to me to be continued support for why we should drop syslog support entirely and move to a more sensible logging framework.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
-
Howard Chu -
Michael Ströder -
Quanah Gibson-Mount