The patch is risky. After it's been applied, invoking
"/etc/init.d/slapd start" while slapd is running can (and most
probably will) result in data loss.
"db4.2_recover -e" will pick up new DB_CONFIG settings, so there's no
need to special-case it for updates.
The patch is risky. After it's been applied, invoking
"/etc/init.d/slapd start" while slapd is running can (and most
probably will) result in data loss.
"db4.2_recover -e" will pick up new DB_CONFIG settings, so there's no
need to special-case it for updates.