Am Sat, 26 Dec 2009 11:11:58 +0800 schrieb Jerome BENOIT <jgm...@rezozer.net>:
> Nevertheless, the error message seems not related, and That's what you usually get when there is a bug. WebDAV-servers send a HTTP-status-code and clients like davfs2 have to rely on it to check wether the request succeeded or what the reason for a failure is. A server with a broken LOCK-implementation does not send a "I HAVE GOT A BROKEN LOCK IMPLEMENTATION"-status-code but something unrelated. You get error "Resource temporarily unavailable" when - the request times out (without any reply from the server) - the server sends status code "408 Request Timeout" - or status code "504 Gateway Timeout" Only in the case of common server bugs davfs2 may be able to do a reasonable guess from a sequence of requests about the real reason for the failure. To see wether davfs2 could do more but translate the HTTP-status-code into a reasonable file system error I would need some more information. To get this information you could - add option "debug most" to your davfs2.conf file - do an as simple as possible file system call that shows the error (mount, cp, unmount) - send the debug messages from your syslog or debug log-file. Although the WebDAV protocol clearly defines how servers can anounce what parts of the protocol they support and what not, it seems to be common practice with many new WebDAV-backends to announce support for anything but to only support a small part of the protocol. Sending a bug report to the maintainer of the server is the most important action to take. Cheers Werner (upstream maintainer) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
