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
hello toby,
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
Hi Benjamin,
On 04/22/2009 10:00 AM Benjamin Eberlei wrote:
> its the locking. A Cachegrind analysis shows usleep() taking up 99,99% of
> the execution time. I have that one at home though, so i can only send it
> to you later this day. How is file locking implemented? are there .lock
> files of
Hello Toby,
its the locking. A Cachegrind analysis shows usleep() taking up 99,99% of
the execution time. I have that one at home though, so i can only send it
to you later this day. How is file locking implemented? are there .lock
files of all the files in the filesystem? Is it a good idea to re
Hi Benjamin,
On 04/21/2009 10:47 PM Benjamin Eberlei wrote:
> i am trying the WebDav component and stumpled accross a weird problem. I
> setup
> a server with file backend to a random dir on my pc and want to access it
> either with Konquorer or with Cadaver. Both clients do send either a PROP
Hello everyone,
i am trying the WebDav component and stumpled accross a weird problem. I setup
a server with file backend to a random dir on my pc and want to access it
either with Konquorer or with Cadaver. Both clients do send either a PROPFIND
or OPTIONS but then somehow get into an infinite
