(ITS#7664) LMDB: Opening a non existing environment with MDB_RDONLY leaves a stale lock file

Full_Name: Salvador Ortiz Version: 24 OS: Linux URL: Submission from: (NULL) (187.162.45.111) Trying to open a non existent environment using MDB_RDONLY, fails with ENOENT as expected, but the lock file is created and is preserved, an issue of pollution IMHO. The problem lies in the unconditional use of O_CREATE in mdb_env_setup_locks. I'm not sure what is the best solution.