I'm grateful for your reply, since you seem the best able to figure out what's
wrong with Apache.
> You redefine DavLockDB in your webdav.conf with
> DavLockDB ${_WEBDAV_FOLDER}/DavLockDB
> So remove this line from your webdav.conf to use DavLockDB from dav_fs.conf
I *knew* you were going to say that, although I would have been very annoyed if
that were the (only) problem. A proper error message would be "DavLockDB
redefined" as opposed to "Vague write error. You're on your own," especially
considering that `apache2ctl configtest` yields no errors.
Needless to say, it still doesn't work with this change enacted. As a reminder,
apache2/error.log reads:
[dav:error] [pid Y:tid Y] [client 127.0.0.1:46XXX] Unable to PUT new contents
for /webdav/test-text-file.txt. [500, #0]
[dav:error] [pid Y:tid Y] (30)Read-only file system: [client 127.0.0.1:46XXX]
An error occurred while opening a resource for writing:
/var/www/html/webdav/test-text-file.txt. [500, #0]
Should I file a bug?
