diff options
| author | Noriko Hosoi <nhosoi@redhat.com> | 2006-04-18 18:25:02 +0000 |
|---|---|---|
| committer | Noriko Hosoi <nhosoi@redhat.com> | 2006-04-18 18:25:02 +0000 |
| commit | 61a3e9ef02b49a8a987b366188d9db05e5449aa0 (patch) | |
| tree | f1418d3dd87139da3f63e8fff336ff9078055117 /ldap/admin | |
| parent | 1eec89b8486f1e5d710f73e494557cab2670acd7 (diff) | |
[189264] 6.11->6.21 upgrade, no db housekeeping threads
The problem was check_db_version finds the existing DBVERSION is old and set
dblayer_private->blayer_recovery_required = 1. If it's set,
DBLAYER_CLEAN_RECOVER_MODE is processed properly. Unfortunately, it was
"reinitialized" in the function read_metadata, which is called after
check_db_version.
Diffstat (limited to 'ldap/admin')
0 files changed, 0 insertions, 0 deletions