Hi all
I'm on apache 2.0.63, and seeing nonsensical Dav Locks
(symptoms are that files show as being locked by users that couldn't
possibly have locked them).
I *think* I've tracked it down to a bug in mod_dav_fs; it appears that
if files are deleted
from disk (by a mechanism other than Dav),
to delete 'file' (e.g. a cronjob)
* PUT newfile (very good chance the inode is reused)
* LOCK newfile (it will fail)
* PROPGET newfile (you'll see it has the same locktoken)
Should I report this as a bug?
On Wed, Oct 14, 2009 at 2:47 PM, Dick Davies
rasput...@hellooperator.net wrote:
Hi all
I'm
Is that documented anywhere at all?
In any event, does it made sense to use something other than the
inode as the key into the lockDB - the URI for example?
On Thu, Oct 15, 2009 at 3:33 PM, Joe Orton jor...@redhat.com wrote:
Steps to reproduce:
* PUT file
* LOCK file
* PROPGET file (note
On Sun, Oct 18, 2009 at 8:50 PM, Stefan Fritsch s...@sfritsch.de wrote:
On Thursday 15 October 2009, Dick Davies wrote:
In any event, does it made sense to use something other than the
inode as the key into the lockDB - the URI for example?
Is the performance improvement of inode keyed
