https://bugzilla.redhat.com/show_bug.cgi?id=430368
Resolves: bug 430368
Bug Description: Due to a spec file problem, the permissions of the
nsslapd-rundir directory can get reset. This causes DS to complain
about it's stats file when starting up.
Reviewed by: ???
Files: see diff
Branch: HEAD
Fix Description: The fix adds a check at startup to see if the user ns-slapd
is running as has read and write permissions on nsslapd-rundir. A
detailed
error message is output if there is an access problem, which instructs the
administrator how to fix it.
Platforms tested: F9
Flag Day: no
Doc impact: no
QA impact: should be covered by regular nightly and manual testing
New Tests integrated into TET: none
https://bugzilla.redhat.com/attachment.cgi?id=326832&action=diff
https://bugzilla.redhat.com/show_bug.cgi?id=432135
Resolves: bug 432135
Bug Description: When the stats file can't be accessed at startup, we
log a message to the terminal that is starting the server. We should
be writing this message to the errors log instead, as you can't see
the message from the terminal if you hit this problem during an
install.
Reviewed by: ???
Files: see diff
Branch: HEAD
Fix Description: Log the message to the errors log.
Platforms tested: F9
Flag Day: no
Doc impact: no
https://bugzilla.redhat.com/attachment.cgi?id=326777&action=diff
https://bugzilla.redhat.com/show_bug.cgi?id=238762
Resolves: bug 238762
Bug Description: Support "auto" for "Import cache size" in the LDBM
Plug-in Settings
Reviewed by: ???
Files: see diff
Branch: HEAD
Fix Description: Added a check box for "use auto cache size". If this
is checked, a value of -1 will be saved for
nsslapd-import-cache-autosize which will tell the server to use the
default auto cache value. If this is not checked, a value of 0 will be
saved which will tell the server to use the number from
nsslapd-import-cachesize. If the check box is checked, the import
cachesize field will be disabled. Here are a couple of screen shots.
https://bugzilla.redhat.com/attachment.cgi?id=326699https://bugzilla.redhat.com/attachment.cgi?id=326700
Platforms tested: RHEL5
Flag Day: no
Doc impact: yes - will have to document the new UI
https://bugzilla.redhat.com/attachment.cgi?id=326701&action=diff
https://bugzilla.redhat.com/show_bug.cgi?id=201332
Resolves: bug 201332
Bug Description: The password modify extop is not allowed when a
password change is required (expired, etc.). This operation
should be allowed.
Reviewed by: ???
Files: see diff
Branch: HEAD
Fix Description: The fix is to let extended operations pass through
connection_need_new_password(), then check if the extended operation
is the password modify extop if a password is expired in do_extended().
If the extended operation is something else, we return an error 53
along with the password expired control.
Platforms tested: F9
Flag Day: no
Doc impact: no
https://bugzilla.redhat.com/attachment.cgi?id=326682&action=diff
https://bugzilla.redhat.com/show_bug.cgi?id=177334
Resolves: bug 177334
Bug Description: LDBM Plug-in Settings console UI value checking issues
Reviewed by: ???
Files: see diff
Branch: HEAD
Fix Description: The code was unconditionally resetting the field before
checking the result of the modify operation. The correct way to do it
is to reset the field only after the modify operation succeeded. I
create a Vector of fields that are being modified, and only reset them
if the modify succeeded.
Platforms tested: RHEL5
Flag Day: no
Doc impact: no
https://bugzilla.redhat.com/attachment.cgi?id=326639&action=diff