Full_Name: Дилян Палаузов Version: 2.4 OS: Linux URL: Submission from: (NULL) (103.252.202.53)

Debugging and logging are different things: logging is more used to avoid problems, that could have happened in the past, while debugging is for reproducing problems in order to resolve them.

https://www.openldap.org/doc/admin24/runningslapd.html#Command-Line%20Option... says -d sets the debug level, and 'Note: slapd must have been compiled with --enable-debug defined for any debugging information beyond the two stats levels to be available (the default).'

Is --enable-debug passed by default, unless one calls --disable-debug, or are the two stats levels combined as 256 | 512 the default debug level?

https://www.openldap.org/doc/admin24/troubleshooting.html#Debugging%20%7B%7B... that 256 is a good firstlevel, not stating whether this is the default or needs to be set explicitly.

https://www.openldap.org/doc/admin24/tuning.html#Logging says the default log level is 256, but does not state how to change it.

https://www.openldap.org/doc/admin24/slapdconfig.html#Global%20Directives presents the same table, as the first link I mentioned here, but calls it 'logging debugging statements' and while the directive is 'loglevel', the table is called 'debugging levels'. It says further:

Default: loglevel stats Basic stats logging is configured by default. However, if no loglevel is defined, no logging occurs (equivalent to a 0 level).

- Does this mean, that no logging occurs, when the loglevel directive is missing, and when it is present without value, the value is stats/256?

Likewise for https://www.openldap.org/doc/admin24/slapdconf2.html#cn=config .

- Please clarify on every place, where loglevel is mentioned, that the default is 256/stats.

- Either use only the term debugging in the whole documentation, or only the term logging, or if both terms are used, clarify the difference between them