[Skunkdav-dev] Re: Help with SkunkDAV

[Jacob S. <smu...@sm...>]

Hi --

First of all, I recommend getting the latest development build from
http://skunkdav.sf.net/, if you don't have it.  In previous versions, 
there was a bug involving any locking operations for servers where basic 
auth wasn't being used.

That shouldn't affect move, copy, or mkcol.  What errors are you getting?

Information that would be useful would be:

1. if you run skunkdav with debugging enabled, any errors in the debug log.
To turn on debugging, try starting it like so:

java -DdefaultDebugLevel=3 -jar skunkdav.jar

There are other more precise ways of doing it, but that should be enough to
catch any errors.  A log called "skunk.log" will appear in the working
directory.

2. An http log.  My current favorite way of generating this (on Linux -- I'm
not sure what you would do on non-Unix platforms) is by using Ethereal, from
www.ethereal.com -- wonderful tool.  Or you can interpose a logging proxy
server between SkunkDAV and the mod_dav server; or you can turn logging way
way up on SkunkDAV (I forget what number you need to use -- maybe 9) and all
the WebDAV XML exchanges will be displayed for you graphically, in JTrees
inside dialogs -- nifty for about five seconds, and then incredibly annoying.

3. Are you seeing errors in your apache log?  Your configuration looks like
the filename for your lock database is "var", which would normally be the
name of a directory.  However, apache doesn't create that directory by
default, so, although I believe that is a mistake and you should probably give
a more descriptive filename underneath the var directory, it might be okay.
However, if you run apache as user/group "nobody", say, and that user can't
create a file called "var" in /usr/local/apache, then mod_dav would fail
fairly catastrophically.  Note that although the DAVLockDB directive
requires a path to a file, not a directory, it will actually create more than 
one file, which might be somewhat confusing.  The normal thing to do would
be to create a directory, /usr/local/apache/var, or something else, and
tweak its permissions/ownership so that the user/group of the httpd process
can read, write and create files in it.

Generally speaking, you should determine whether you are having SKunkDAV
problems or mod_dav problems.  Use of the cadaver command-line client for
comparison would be a good idea.  If you are having mod_dav problems that the
above suggestions don't clear up, the dav_dev list at webdav.org is a helpful 
resource.

Perhaps it doesn't fit with the needs of your project, but I recommend using
some sort of authentication.  Basic is the easiest, and SkunkDAV supports it.
You don't want everyone on the internet to upload and delete on your server.

Good luck,

Jacob Smullyan


On Sat, Jun 16, 2001 at 08:38:12PM -0700, Hiroshi Natsu Cardenas wrote:
> 
> Hi
> 
> I am interested in work with the client API that you desing in an final 
> proyect for a class.
> 
> I have already installed the Apache with mod_dav and it is running, I 
> tried to configure a directory to suport webDAV I put the following lines 
> inside the httpd.conf file :
> 
> DAVLockDB /usr/local/apache/var
> DAVMinTimeout 10
> 
> <Directory "/usr/local/apache/htdocs/webdav">
> DAV on
> </Directory>
> 
> finally I ran the skunkdav with the line '$java -jar skunkdav.jar' and I 
> can connect with the server and see the files but i can not do any 
> operation like move, copy, mkcol, etc... 
> 
> I think that the problem may  be with the users allowed, 
> 
> can you help me
> 
> Thanks Hiroshi
> 

--