[sorry for the crosspost, but not sure where this should go]. To answer my own question: got to the bottom of it; looks to me like the lock DB is a hash of inode <-> locktoken Steps to reproduce: * PUT file * LOCK file * PROPGET file (note down the locktoken) use something 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 <rasputnik@xxxxxxxxxxxxxxxxx> wrote: > 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), any locks that were taken > out on that file > 'jump' so that they apply to a different file altogether. > > Are there any tools that let me inspect the content of DavLockDB? And > who's a good person > to talk to if I need to pick over the code? > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|