Red Hat Bugzilla – Bug 1319329
add nsslapd-auditlog-logging-enabled: off to template-dse.ldif
Last modified: 2016-11-03 16:40:38 EDT
Description of problem: This is a request to add nsslapd-auditlog-logging-enabled: off to the configuration file /usr/share/dirsrv/data/template-dse.ldif This is mostly for convenience, when one has to find out a parameter name and syntax, this was about to have nsslapd-auditlog-logging-enabled turned on by default. It could be a more general request, to have all tunables tha thave default values listed by default in a dse.ldif, that can help reviewing configurations for tuning. I kind of agree to have "nsslapd-auditlog-logging-enabled: off" and others listed in dse.ldif, it always take time to figure out the name, specially as more knobs are added over time. Version-Release number of selected component (if applicable): 389-ds-base-1.3.4.0-21.el7_2.x86_64 How reproducible: N/A Steps to Reproduce: 1. N/A 2. 3. Actual results: Expected results: Additional info:
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
RHEL: RHEL 7.3 x86_64 Server DS builds: [root@ds ~]# rpm -qa | grep 389-ds-base 389-ds-base-libs-1.3.5.10-5.el7.x86_64 389-ds-base-debuginfo-1.3.5.8-1.el7.x86_64 389-ds-base-1.3.5.10-5.el7.x86_64 389-ds-base-snmp-1.3.5.10-5.el7.x86_64 Steps performed: 1. Verified whether 'nsslapd-auditlog-logging-enabled: off' was added to template-dse.ldif file [root@ds ~]# grep 'nsslapd-auditlog-logging-enabled: off' /usr/share/dirsrv/data/template-dse.ldif nsslapd-auditlog-logging-enabled: off 2. Created a standalone DS instance 3. Verified whether 'nsslapd-auditlog-logging-enabled: off' [root@ds ~]# grep 'nsslapd-auditlog-logging-enabled: off' /etc/dirsrv/slapd-master1/dse.ldif nsslapd-auditlog-logging-enabled: off As can be seen above, the required configuration parameter has been added to both template-dse.ldif and dse.ldif files
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2594.html