Greetings, Are there requirements or assumptions for the m2 dir handler/service? On relatively rare occasions (I am not sure how to reproduce this) the contents of another file gets served. An annoying example is getting the contents of a seemingly random file (somewhere in the served directory tree) sent for a css file. Is it reasonable to serve static content (via m2) from a heavily used NFS mount? Does someone have any ideas how I could stress the cache and try to reproduce this bug enough to debug it?
Note, so far, apache seems to be handling the static content fine (for several weeks). Anecdotally, we used to have major issues with mod_python having similar issues on the same system. However, tools like uwsgi and mod_php or mod_wsgi didn't exhibit such issues. Maybe this is because uwsgi and mod_wsgi don't monitor multiple files for reloading. One issue with NFS mount might be that inodes are not a reliable method of determining the status of a file. Jeff Van Voorst
