Hi Ben,
On Thu, Sep 25, 2008 at 11:36:44AM -0700, Ben Poliakoff wrote:
[..snip..] 
> And /var/spool/caldavd/principals/users/benp is not created (even though
> the caldavd user has full privs on the /var/spool/caladavd directory).
What filesystem is this? You do have to set user_xattr:
 /usr/share/doc/calendarserver/README.Debian
but the error should look different then.

> Trying with another caldav client Thunderbird/Lightning (using the url
> "https://host.name.here:8443/calendars/users/benp/calendar/"; since
> Lightning doesn't support the /principals stuff yet) my calendar is
> marked as unavailable.  Here are access.log entries from calendarserver
> as I try to an event (*nothing* shows up in the error.log):
> 
> 134.10.15.21 - - [25/Sep/2008:11:13:02 -0700] "PUT \
>     /calendars/users/benp/calendar/36cd9363-ffe6-4afd-9de2-0998e3f4f6ed.ics \
>     HTTP/1.1" 404 186 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; \
>     rv:1.8.1.16)  Gecko/20080707 Lightning/0.9 Thunderbird/2.0.0.16" [190.6 \
>     ms]
> 134.10.15.21 - - [25/Sep/2008:11:14:10 -0700] "PROPFIND
>     /calendars/users/benp/calendar/ HTTP/1.1" 404 146 "-" "Mozilla/5.0 (X11; \
>     U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080707 Lightning/0.9 Thund \
>     erbird/2.0.0.16" [196.0 ms]
> 134.10.15.21 - - [25/Sep/2008:11:14:11 -0700] "OPTIONS \
>     /calendars/users/benp/ HTTP/1.1" 404 137 "-" "Mozilla/5.0 (X11; U; Linux \
>     i686; en-US; rv:1.8.1.16) Gecko/20080707 Lightning/0.9 Thunderbird/2.0 \
>     .0.16" [232.1 ms]
> 
> The PROPFIND/OPTIONS lines go on continuously until I quit Thunderbird.
They show up every second?

What's displayed if you go to:
 https://host.name.here:8443/calendars/users/benp/calendar/
with firefox? The calendar should be provisioned then too.

Could you doublecheck the permissions on /var/spool/caladvd - maybe by
        su -s /bin/bash caldavd
        touch /var/spool/caldvd/test
Cheers,
 -- Guido



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to