Hi everyone!
I don't know if this is intended or not, but when I run OpenLDAP with logs attached on stderr, like:
./slapd -h 'ldap://*:389 ldaps://*:636' -F ./slapd.d -u ldap -g ldap -d 256
the logs do not enforce olcLogFileFormat.
For example:
68b6fe23.27b26379 0x7fe756a70e40 @(#) $OpenLDAP: slapd 2.6.10 (May 21 2025 22:00:00) $
instead of:
Sep 02 16:21:50 hostname slapd[12345]: slapd starting
Is this the expected behaviour? If so, are there any plans for having an option to set the date in stderr logs?
Thanks in advance for any response!
Regards,
David Coutadeur wrote:
Hi everyone!
I don't know if this is intended or not, but when I run OpenLDAP with logs attached on stderr, like:
./slapd -h 'ldap://*:389 ldaps://*:636' -F ./slapd.d -u ldap -g ldap -d 256
the logs do not enforce olcLogFileFormat.
stderr is for debug messages only. It is not "logs" and therefore none of the logging directives affect it.
For example:
68b6fe23.27b26379 0x7fe756a70e40 @(#) $OpenLDAP: slapd 2.6.10 (May 21 2025 22:00:00) $
instead of:
Sep 02 16:21:50 hostname slapd[12345]: slapd starting
Is this the expected behaviour? If so, are there any plans for having an option to set the date in stderr logs?
Thanks in advance for any response!
Regards,
Hello,
Le 17/09/2025 à 15:57, Howard Chu a écrit :
David Coutadeur wrote:
Hi everyone!
I don't know if this is intended or not, but when I run OpenLDAP with logs attached on stderr, like:
./slapd -h 'ldap://*:389 ldaps://*:636' -F ./slapd.d -u ldap -g ldap -d 256
the logs do not enforce olcLogFileFormat.
stderr is for debug messages only. It is not "logs" and therefore none of the logging directives affect it.
Ok, thanks for the clarification.
I think it could be interresting to have a parameter for this.
For example, with containerization, it is considered as a good practice to make the main process send logs directly to stdout
Regards,
For example:
68b6fe23.27b26379 0x7fe756a70e40 @(#) $OpenLDAP: slapd 2.6.10 (May 21 2025 22:00:00) $
instead of:
Sep 02 16:21:50 hostname slapd[12345]: slapd starting
Is this the expected behaviour? If so, are there any plans for having an option to set the date in stderr logs?
Thanks in advance for any response!
Regards,
David Coutadeur wrote:
Hello,
Le 17/09/2025 à 15:57, Howard Chu a écrit :
David Coutadeur wrote:
Hi everyone!
I don't know if this is intended or not, but when I run OpenLDAP with logs attached on stderr, like:
./slapd -h 'ldap://*:389 ldaps://*:636' -F ./slapd.d -u ldap -g ldap -d 256
the logs do not enforce olcLogFileFormat.
stderr is for debug messages only. It is not "logs" and therefore none of the logging directives affect it.
Ok, thanks for the clarification.
I think it could be interresting to have a parameter for this.
For example, with containerization, it is considered as a good practice to make the main process send logs directly to stdout
Then you could just use `logfile /dev/stdout` or somesuch.
Regards,
For example:
68b6fe23.27b26379 0x7fe756a70e40 @(#) $OpenLDAP: slapd 2.6.10 (May 21 2025 22:00:00) $
instead of:
Sep 02 16:21:50 hostname slapd[12345]: slapd starting
Is this the expected behaviour? If so, are there any plans for having an option to set the date in stderr logs?
Thanks in advance for any response!
Regards,
Hello,
Le 17/09/2025 à 16:39, Howard Chu a écrit :
David Coutadeur wrote:
Hello,
Le 17/09/2025 à 15:57, Howard Chu a écrit :
David Coutadeur wrote:
Hi everyone!
I don't know if this is intended or not, but when I run OpenLDAP with logs attached on stderr, like:
./slapd -h 'ldap://*:389 ldaps://*:636' -F ./slapd.d -u ldap -g ldap -d 256
the logs do not enforce olcLogFileFormat.
stderr is for debug messages only. It is not "logs" and therefore none of the logging directives affect it.
Ok, thanks for the clarification.
I think it could be interresting to have a parameter for this.
For example, with containerization, it is considered as a good practice to make the main process send logs directly to stdout
Then you could just use `logfile /dev/stdout` or somesuch.
Indeed. Thanks for the tip.
Regards,
For example:
68b6fe23.27b26379 0x7fe756a70e40 @(#) $OpenLDAP: slapd 2.6.10 (May 21 2025 22:00:00) $
instead of:
Sep 02 16:21:50 hostname slapd[12345]: slapd starting
Is this the expected behaviour? If so, are there any plans for having an option to set the date in stderr logs?
Thanks in advance for any response!
Regards,
openldap-technical@openldap.org
-
David Coutadeur -
Howard Chu