#48969 nsslapd-auditfaillog always has an explicit path
Closed: Fixed None Opened 2 years ago by nhosoi.

In the current implementation, nsslapd-auditfaillog is not set, by default. Internally, the value is NULL, which let audit fail log share the same audit log file with nsslapd-auditlog.

Once, some path is set to nsslapd-auditfaillog, it is not allowed to delete or set NULL or empty to it. That is, there is no way to go back to the default behaviour.

There is another issue for the default value. Since search for nsslapd-auditfaillog under cn=config does not return anything, it is hard to find out where the failed logs are written.


Thank you for reviewing the patch, William!

Pushed to master:
fda0043..ef2c3c4 master -> master
commit ef2c3c4

{{{
Description: commit ef2c3c4
introduced a RESOURCE_LEAK.
auditlog.c:180: leaked_storage: Variable "audit_config" going
out of scope leaks the storage it points to.
}}}

Pushed to master:
32ee33b..b0fc822 master -> master
commit b0fc822

Pushed to 389-ds-base-1.3.5:
cf5683a..fc1310e 389-ds-base-1.3.5 -> 389-ds-base-1.3.5
commit fc1310e

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.5.13

2 years ago

Login to comment on this ticket.

Metadata