Hey, please add me to CC next time - for some reason the BTS did not do this, and I only found your reply by accident.
On Sun, 17 Jan 2016 10:11:24 +0530 Rahul Amaram <[email protected]> wrote: > [..] > > If I do pass the "-u caldavd -g caldavd" arguments (caldavd -X -u > caldavd -g caldavd) and remove the user and group information in > /etc/caldavd/caldavd.plist, I see the following: > > # ls -al /var/run/caldavd/ > total 12 > drwxr-xr-x 2 caldavd caldavd 180 Jan 17 08:51 . > drwxr-xr-x 16 root root 580 Jan 16 18:46 .. > -rw-r--r-- 1 root root 5 Jan 17 08:51 caldavd.pid > srw-rw---- 1 root root 0 Jan 17 08:51 caldavd.sock > -rw-r--r-- 1 caldavd caldavd 5 Jan 17 08:51 caldav-instance-0.pid > -rw-r--r-- 1 caldavd caldavd 5 Jan 17 08:51 caldav-instance-1.pid > srw-rw---- 1 caldavd caldavd 0 Jan 17 08:51 directory-proxy.sock > lrwxrwxrwx 1 caldavd caldavd 5 Jan 17 08:51 directory-proxy.sock.lock > -> 28420 > srwx------ 1 caldavd caldavd 0 Jan 17 08:51 memcache.sock > > In this case, calendarserver works properly but the error.log shows > permission denied error as the caldavd user does not have permissions > for caldavd.sock file. To address this issue, I have configured the user > and group in /etc/caldavd/caldavd.plist as well. Now I get the drop > privileges warning, but there are no Permission denied errors in error.log. > > So, I have decided to call the caldavd daemon with username and group > arguments and at the same time have the same username and group > configured in /etc/caldavd/caldavd.plist > Looks like you are right, I see the same thing on my machine with 5.2.2+dfsg-2. My error.log.* are several MB long, and I didn't notice that before. Your fix sounds good, one warning is better than many error messages. :) Thanks! X
