Open dylanwoo opened 11 years ago
opengeek
commented
11 years ago opengeek submitted:
Another attempt at solving this using link() instead of rename() available for download and testing...
http://modx.s3.amazonaws.com/releases/2.2.7/modx-2.2.7-dev-20121228.zip http://modx.s3.amazonaws.com/releases/2.2.7/modx-2.2.7-dev-20121228-advanced.zip
modxbot
commented
11 years ago rethrash submitted:
I'm not sure we're going to ever make headway on this since it's an issue of the core system architecture for RSCS: http://tracker.modx.com/projects/revo/issues?query_id=134
If anyone from Rackspace can contribute to resolving this or someone else can create a workaround, we'd SERIOUSLY welcome the input.
dylanwoo created Redmine issue ID 9272
See this
http://forums.modx.com/thread/80423/modx-having-a-hard-time-on-rackspace-cloud?page=2#dis-post-446916
even though the newer versions of Modx is giving the ability to disable flock, it appears that the application is still using flock. I still see errors "Exclusive locks are not supported for this stream" on a site that has had flock disabled using the new variables in the latest version (./core/xpdo/xpdo.class.php: const OPT_USE_FLOCK = 'false'; )
On a host such as GoDaddy, you probably won't see the file corruption because of their single node environment (we use a multi node environment).
Speaking of multi node, Modx looks to be using the process PID, which won't work reliably on our environment as the same PIDs can be re-used at the same time in our environment on the different nodes. A more reliable process might be to use the hostname/servername in conjuction with the PID.