[CalendarServer-users] Getting a stable version of Calendar Server?
Scott Buchanan
dscottbuch at mac.com
Mon Aug 31 17:18:00 PDT 2009
I removed the older installation and re-installed the server from
scratch. After doing this, using the run -i / command, I still had to
correct two problems I've had in the past.
1) caldavd - in the caldavd produced the PYTHONPATH defined is
PYTHONPATH="Library/Python/2.6/site-packages/:$PYTHONPATH"
Note the missing initial "/". Nothing at all works without changing
this.
2) After fixing the above when running the server it fails. Reported
in the error log (or Console I'm not sure) is that it can't find /usr/
share/caldavd/bin/twistd. I grep'd through the code and can't find
where this is referenced so I fixed it by aliasing /usr/share/caldavd
to /usr/local. Then all works just fine.
I'm sure I'm doing something incorrect in configuration or build but I
can't find where. (1) seems like a bug but its been like this for
years.
Thanks,
Scott
On Aug 31, 2009, at 7:55 AM, Cyrus Daboo wrote:
> Hi Scott,
>
> --On August 29, 2009 1:59:22 PM -0700 Scott Buchanan <dscottbuch at mac.com
> > wrote:
>
>> OK. I tracked this down to a permissions issue on /var/run/caldavd
>> and
>> the files calendaruserproxy.sqlite & resourceinfo.sqlite. By adding
>> group rw permissions to this directory and these files the following
>> error no longer occurs and all seems to be working. I have no idea
>> what
>> security risk this presents as I currently don't understand the
>> security
>> model of CalendarServer so I don't know if this is a legitimate fix
>> or
>> not.
>>
>> Any input appreciated.
>
> First off in the new code we put those .sqlite files in a new
> location by default: /Library/CalendarServer/Data/. It is best not
> to use /var/run/ for those as they are "persistent" database files
> and should not be automatically purged (as might happen to something
> in /var/run).
>
> On permissions, the best thing is to create a "calendar" user and
> group for your system, and change the caldavd.plist to use those.
> Ensure that /Library/CalendarServer's contents have read-write for
> that user and group. You will need to start the server as the admin
> user but it will drop privileges to the user and group you specify.
>
> --
> Cyrus Daboo
>
More information about the calendarserver-users
mailing list