I've been happily running WPSearch (188.8.131.52) - great plugin so big thanks for all the work that has gone into it.
In my spare time I have been working on some alternatives to harden WordPress installs - basically by splitting the administration tasks off onto an entirely separate web server (Apache in my case).
In a nutshell, I set it up so that the administrative instance of Apache is the only one that can actually write to the disk; it runs under a different UID to the "end user" Apache, which only ever has read access.
This generally works great, although obviously fails when anything running in "end user space" needs to write to the disk. For example, WPSearch seems to need to write to the disk in the WPSearch/Backends/Phplucene/data directory (some sort of read lock file).
I am guessing this might be a Lucene-level requirement, but I was curious to know if this might be avoidable, either by removing the lock altogether or moving it into the database?
Thanks for any feedback!