-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Filesystem API
-
Storage Engines - Persistence
-
51.098
-
StorEng - Defined Pipeline
-
None
Some customers want to be able to open WT on a read only file system. If a lock file exists, WT tries to open it read/write and gets an EPERM error, causing the system to fail.
In this scenario it should be safe to ignore the EPERM, since we know that we won't be able to change the database.