Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1708215
Description of problem: nsslapd-accesslog-maxlogsperdir | nsslapd-errorlog-maxlogsperdir | nsslapd-auditlog-maxlogsperdir All the attributes are accepting the negative value, which is not in the correct range. Version-Release number of selected component (if applicable): 389-ds-base-1.3.9.1-5.el7.x86_64 How reproducible: Every time Steps to Reproduce: 1. ldapmodify -x -p 389 -h `hostname` -D "cn=Directory Manager" -w password << EOF dn: cn=config changetype: modify replace: nsslapd-auditlog-maxlogsperdir nsslapd-auditlog-maxlogsperdir: -5 EOF 2. ldapmodify -x -p 389 -h `hostname` -D "cn=Directory Manager" -w password << EOF dn: cn=config changetype: modify replace: nsslapd-accesslog-maxlogsperdir nsslapd-accesslog-maxlogsperdir: -5 EOF 3. ldapmodify -x -p 389 -h `hostname` -D "cn=Directory Manager" -w password << EOF dn: cn=config changetype: modify replace: nsslapd-errorlog-maxlogsperdir nsslapd-errorlog-maxlogsperdir: -5 EOF Actual results: Accepting all negative value. Expected results: Should not accept -5 or any other negative value other than -1. Additional info: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/ configuration_command_and_file_reference/Core_Server_Configuration_Reference#cn config-nsslapd_errorlog_logrotationtime_Error_Log_Rotation_Time
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1708215
Metadata Update from @mreynolds: - Issue assigned to mreynolds
https://pagure.io/389-ds-base/pull-request/50395
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.3.9 (was: 0.0 NEEDS_TRIAGE)
commit ca70d06fbb7a2c06c62f0ba5b192dba36f24b8e3
f76845fe9..2e749e722 389-ds-base-1.4.0 -> 389-ds-base-1.4.0
8b279b492..a50a86547 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3451
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)