Using Process Monitor I verified that the DB_CONFIG is actually read by
bitcoind.
If any one willing to try it out, here is the list of wallets you can drop into your bitcoin.conf: to reproduce
https://pastebin.com/8wHD1tL3EDIT:
From the Berkeley DB documentation:
https://docs.oracle.com/cd/E17276_01/html/api_reference/C/set_lk_max_locks_parameter.htmlIf the database environment already exists when this parameter is changed, it is ignored. To change this value after the environment has been created, re-create your environment.
What to make of this? is it impossible to change this parameter b/c the database environment already exists? or did I miss-read?