On Wed, 22 Apr 2009, Benjamin Eberlei wrote: > On Wednesday 22 April 2009 10:08:28 Tobias Schlitt wrote: > > > > There is a global lock file for the whole back end directory, which is > > used when you acquire or release a Webdav lock or perform certain > > operations on locked entities. The lock only lasts for a certain part of > > the request. > > > > Locking is neccessary here, since the lock plugin performs multiple > > requests on the backend, which must occur like an atomic operation. > > > > You're right, it should be in the hand of an admin to free such dangling > > locks, if they occur. You can simply delete them and the server should > > be running properly again. > > > > If you experience this issue reproducably again, please trace it and > > send me the trace so I can see what's going wrong. > > i tried again today after rebooting my desktop and it did not work out of the > box. the usleep locking routine goes into an infinite loop in usleep. > > Now i have the cause (probably a bug) and it is that the directory was not > +x'able from the server directory. Shouldnt that be checked in the locking > routine at least once upon setting the path with the options?
It should... can you file a report for this so that we don't forget about it please? (Feel free to point to this discussion from your report). with kind regards, -- Derick Rethans eZ components Product Manager eZ systems | http://ez.no -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
