Description of problem:
Chamging the logrotation configuration is not dynamic it requires a server
restart for the changes to take effect e.g.

${LDAPMODIFY} -p ${LDAPport} -h ${LDAPhost} -D "${ROOTDN}" -w ${ROOTDNPW} -acv
<<EOF
dn: cn=config
changetype: modify
replace: nsslapd-errorlog-logrotationtime
nsslapd-errorlog-logrotationtime: 1
-
replace: nsslapd-errorlog-logrotationtimeunit
nsslapd-errorlog-logrotationtimeunit: minute
EOF

${IROOT}/restart-slapd
if [ $? -ne 0 ]; then
    message "RestartSlapd: cannot start slapd"
fi

No doubt making this dynamic would have performance implications. Especially if
it checked the config each time before logging. Bad.

Hallway discussion: perhaps when the rotation thread wakes up; we could check
it
then and reload if needed ?

Version-Release number of selected component (if applicable):
7.1 sp 1

How reproducible:
always

Steps to Reproduce:
1. Modify the log rotation configuration
2. changes do not take effect until the server is restarted

${LDAPMODIFY} -p ${LDAPport} -h ${LDAPhost} -D "${ROOTDN}" -w ${ROOTDNPW} -acv
<<EOF
dn: cn=config
changetype: modify
replace: nsslapd-errorlog-logrotationtime
nsslapd-errorlog-logrotationtime: 1
-
replace: nsslapd-errorlog-logrotationtimeunit
nsslapd-errorlog-logrotationtimeunit: minute
EOF

${IROOT}/restart-slapd
if [ $? -ne 0 ]; then
    message "RestartSlapd: cannot start slapd"
fi


Actual results:

changes do not take effect until the server is restarted

Expected results:
perhaps .... we should automatically pick this change up ?

Additional info: