Good catch, just noticed this myself.
As there is no (documented) way of setting the service GUID, I'm
quite certain you'll be fine with letting DCS generate the GUID for you.
I tried setting the GUID in the following way:
<accounts realm="My Realm" guid="my-hideously-long-guid">
and while this works (the server stops complaining about the missing
GUID), I don't really see the point of it.
Hopefully, the DCS folks will shed some light on this if it has any
significance (for federation purposes or whatever).
/Emil
20 nov 2007 kl. 09.12 skrev Steven Chan:
Hi, folks,
Gaining confidence with DCS, I'm starting to weed out the final
small errors in the log. I see the following:
<snip>
2007-11-19 23:51:45-0800 [-] [caldav-8009] [AMP,client] "Directory
service <XMLDirectoryService 'Test Realm': FilePath('/Users/Steven/
Documents/CalServer/CalendarServer/conf/accounts-test.xml')> has no
GUID; generating service GUID from realm name."
2007-11-19 23:51:45-0800 [-] [caldav-8009] [AMP,client] "Directory
service <SudoDirectoryService 'Test Realm': FilePath('/Users/Steven/
Documents/CalServer/CalendarServer/conf/sudoers.plist')> has no
GUID; generating service GUID from realm name."
<snip>
I'm assuming that I don't need to worry about these errors. I
can't imagine changing these two realm names, so the generated
service GUIDs should remain constant (assuming that they're
generated by a hashing algorithm of some sort).
Safe assumption?
Regards,
Steven
_______________________________________________
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
