#365: caldav is using wrong socket --------------------------------+------------------------------------------- Reporter: guy@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: Component: Calendar Server | Severity: Serious Keywords: | --------------------------------+------------------------------------------- configuring caldav for calendaring and using ./run to start it seems to be hooking into the wrong socket: 2010-03-04 11:33:08+0300 [-] [caldav_task] 2010-03-04 11:33:08+0300 [-] twistd 9.0.0+r27606 (/usr/bin/python 2.5.0) starting up. 2010-03-04 11:33:08+0300 [-] [caldav_task] 2010-03-04 11:33:08+0300 [-] reactor class: twisted.internet.selectreactor.SelectReactor. 2010-03-04 11:33:08+0300 [-] [caldav_task] 2010-03-04 11:33:08+0300 [-] set uid/gid 2/2 2010-03-04 11:33:08+0300 [-] [caldav-0] [-] Log opened. 2010-03-04 11:33:08+0300 [-] [caldav-0] [-] twistd 9.0.0+r27606 (/usr/bin/python 2.5.0) starting up. 2010-03-04 11:33:08+0300 [-] [caldav-0] [-] reactor class: twisted.internet.selectreactor.SelectReactor. 2010-03-04 11:33:08+0300 [-] [caldav-0] [-] set uid/gid 2/2 2010-03-04 11:33:08+0300 [twistedcaldav.accesslog.AMPLoggingFactory] AMPLoggingProtocol connection established (HOST:UNIXSocket('/var/calData/ServerRoot/Run/'''carddavd.sock'''') PEER:UNIXSocket('')) 2010-03-04 11:33:08+0300 [-] [caldav-0] [-] AMP connection established (HOST:UNIXSocket(None) PEER:UNIXSocket('/var/calData/ServerRoot/Run/'''carddavd.sock'''')) This obviously stops you being able to run caldav and carddav on the same system -- Ticket URL: <http://trac.calendarserver.org/ticket/365> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server