https://bugs.openldap.org/show_bug.cgi?id=9505
Issue ID: 9505 Summary: Should be admin guide section on logging detail Product: OpenLDAP Version: 2.5 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: documentation Assignee: bugs@openldap.org Reporter: quanah@openldap.org Target Milestone: ---
Currently we do not document information about the log levels, particularly stats.
For example, we don't document anywhere outside the slap.h header what time units etime and qtime use (microseconds). This would be helpful, since other directory servers use (and DOCUMENT) milliseconds.
Overall it would likely be helpful to end users so they understand more about what the information stats logging is providing.
https://bugs.openldap.org/show_bug.cgi?id=9505
--- Comment #1 from Howard Chu hyc@openldap.org --- The timestamps are decimal numbers to 6 decimal places. If they don't understand decimal places no admin guide text is going to help them.
https://bugs.openldap.org/show_bug.cgi?id=9505
--- Comment #2 from Quanah Gibson-Mount quanah@openldap.org --- (In reply to Howard Chu from comment #1)
The timestamps are decimal numbers to 6 decimal places. If they don't understand decimal places no admin guide text is going to help them.
ODSEE's etime is 6 decimal places too, they just only use 3 of them. ;)
https://bugs.openldap.org/show_bug.cgi?id=9505
--- Comment #3 from Quanah Gibson-Mount quanah@openldap.org --- Regardless, the overall point is to document what exactly is being logged. What does qtime= mean? what does etime= mean? What does op= mean? etc.
https://bugs.openldap.org/show_bug.cgi?id=9505
--- Comment #4 from Howard Chu hyc@openldap.org --- (In reply to Quanah Gibson-Mount from comment #2)
(In reply to Howard Chu from comment #1)
The timestamps are decimal numbers to 6 decimal places. If they don't understand decimal places no admin guide text is going to help them.
ODSEE's etime is 6 decimal places too, they just only use 3 of them. ;)
How many digits are actually significant is platform-specific, so for all we know there may only be 3 sigfigs on a particular machine running our stuff too. (And on older Windows PCs the system clock only ticked 18 times/second, so it may look like all 6 digits are in use because of the resulting fractions, but really there's only 55ms resolution.) It's not our job to explain to sysadmins how their machines work.