Replies inline. On Oct 29, 2012, at 8:21 PM, calendarserver.s...@spamgourmet.com wrote:
>> No current version of Calendar Server uses PythonDirector. Perhaps you >> should upgrade? > > > Sounds good. Which is considered ready for day-to-day use? > > According to the following link, version 3.0 is in development. > http://trac.calendarserver.org/ In this case, "in development" refers to the documentation, which is pretty much perpetually true. Check the source tree under branches/tags/release for the latest stable release. -dre > > So I had grabbed 2.5 hoping for the "stable" release. > -- > Derek > > > On 29 Oct 2012, at 22:08, Glyph - gl...@twistedmatrix.com > <+calendarserver+sgd2+6968b9041d.glyph#twistedmatrix....@spamgourmet.com> > wrote: > >> No current version of Calendar Server uses PythonDirector. Perhaps you >> should upgrade? >> >> -g >> >> On Oct 29, 2012, at 7:38 PM, calendarserver.s...@spamgourmet.com wrote: >> >>> Hi all, >>> >>> >>> I am trying to determine if this is an error in my configuration, but I >>> think perhaps not. >>> >>> >>> The error message reads: >>> >>> [pydir] pydirector.pdconf.ConfigError: expected 'service' or 'admin', got >>> 'control' >>> >>> This is thrown from pydirector/pdconf.py, PDConf.__init__(self, >>> filename=None, xml=None) >>> >>> The filename is a generated file that in this instance contains a 'control' >>> element as a child of the 'pdconfig' element. >>> >>> This XML file is generated in calendarserver/tap/caldav.py, in >>> CalDAVServiceMaker.makeService_Combined(…)which has code like so: >>> >>> pdconfig = """<pdconfig>%s<control socket="%s" /></pdconfig>""" % ( >>> "\n".join(services), config.PythonDirector.ControlSocket, >>> ) >>> >>> I think this method must be constructing an XML file that cannot be read by >>> PythonDirector. The services are concatenated, but then the ControlSocket >>> element is appended before the closing 'pdconfig' tag. This is evidently >>> unacceptable because the element is a 'control' element and not one of >>> 'service', 'admin', or 'logging'. >>> >>> >>> I am using the control socked suggested in the caldavd-test.xml: >>> >>> <key>ControlSocket</key> >>> <string>logs/caldavd-pydir.sock</string> >>> >>> and the problem element appears in the temporary XML fed to >>> PDConf.__init__(…): >>> <control socket="logs/caldavd-pydir.sock" /> >>> >>> >>> >>> Could anyone advise? >>> >>> >>> >>> Thanks, >>> -- >>> Derek >>> _______________________________________________ >>> calendarserver-users mailing list >>> calendarserver-users@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo/calendarserver-users > > > _______________________________________________ > calendarserver-users mailing list > calendarserver-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/calendarserver-users _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
