>> "db4.2_recover -e" will pick up new DB_CONFIG settings, so there's no
>> need to special-case it for updates.
>
> Are you sure?
Yes, I regularly use "-e" to recreate the environment after tweaking
DB_CONFIG.
> I though "-e" was to retain the old setting?
"-e" does not retain any settings, it retains the environment. The
settings are taken from DB_CONFIG and the compiled-in default values,
not from the previous environment configuration.
* Torsten Landschoff:
>> "db4.2_recover -e" will pick up new DB_CONFIG settings, so there's no
>> need to special-case it for updates.
>
> Are you sure?
Yes, I regularly use "-e" to recreate the environment after tweaking
DB_CONFIG.
> I though "-e" was to retain the old setting?
"-e" does not retain any settings, it retains the environment. The
settings are taken from DB_CONFIG and the compiled-in default values,
not from the previous environment configuration.