One of the reasons, I never got the commandline tools working are those hard wired dependencies.
Would 16.6.0 not work with them?
... and if I explicitly install Twisted 15.4.0, the CLI tools work at least. Try this:
[cs@ ~]$ calendarserver_config DefaultLogLevel
DefaultLogLevel=warn
The above should be similar to what the server actually does to obtain config values. If I change DefaultLogLevel in /usr/local/etc/caldavd.plist, that change is reflected by calendarserver_config.
Also, can you share the command you use to actually start CS?
If you install the package, its in /usr/local/etc/rc.d/caldavd .
I never invoke caldavd directly, and CS changes its process name after launch so you can't just look at it, and newproc.d on OS X will show you processes names and launch args, but not ALL of the args... All my attempts seem to result in:
/usr/local/bin/twistd: Unknown command: caldav
… but I'm surely doing it wrong.
[caldav3:/] root# service caldavd onestart
Starting caldavd.
Reading configuration from file: /usr/local/etc/caldavd/caldavd.plist
[caldav3:/] root# service caldavd onestatus
caldavd is running as pid 10762.
[caldav3:/] root# ps -axlww | grep CalendarServer
0 10762 1 0 20 0 224484 94564 kqread SJ - 0:02.22 python2.7: CalendarServer Combined (python2.7)
639 10764 10762 0 20 0 219220 90872 kqread SJ - 0:06.74 python2.7: CalendarServer Directory Proxy Service (python2.7)
639 10765 10762 0 20 0 232172 97156 kqread SJ - 0:08.22 python2.7: CalendarServer Slave #0 (python2.7)
639 10766 10762 0 20 0 231024 95332 kqread IJ - 0:07.97 python2.7: CalendarServer Slave #1 (python2.7)
0 10817 10689 0 20 0 14796 2472 - R+J 2 0:00.00 grep CalendarServer
[caldav3:/] root#
•
What I want to try is getting CS to run in the 'developer mode' from a git checkout, using the bin/run script. In that state, the location and import order of all the modules should be fairly predictable, and I suspect that might be enough to get the config to load as expected. But, I still have to wade through a bunch of broken stuff to get ./bin/develop to run cleanly. There are some aspects of the ./bin/develop script (and the scripts it sources) that just don’t work very well on BSD.
Yes.
I’m no expert in ports and pkg. Perhaps you get some insight here