I'm thinking also that maybe nothing is wrong server-side. It's just that the first time you try to subscribe to this huge calendar, it takes longer than iCal's 30 second timeout will allow. I found this and similar on google:
http://forums.macosxhints.com/showthread.php?t=86251 We tried subscribing using Lightning and it took 2 minutes, but it worked. So I think there could be something to this. So... I know it's more of a client side question, but anybody know how to increase iCal's timeout interval? I couldn't find it in the plist or in defaults read com.apple.iCal. And I didn't find it in the application bundle, but haven't opened anything in resource or hex editors. I'd like to try this before I delete anybodies calendar data. Cheers, tack On Jun 23, 2008, at 11:39 AM, Cyrus Daboo wrote: > Hi tack, > > --On June 23, 2008 11:12:56 AM -0700 tack <[EMAIL PROTECTED]> wrote: > >> My big question is: How can I revert people's calendars/users to a >> state where they're accessible or 'fresh' if my theory is correct? I >> don't want to irreparably break my test subjects account and if I'm >> right, I want to fix the users who are having problems. Is it as >> simple as commenting them out of accounts.xml, waiting 10 minutes >> then >> uncommenting them? Do I have to do some gnarly SQL-Fu? And worst >> case scenario; can I simply blow away the whole database, restart >> caldavd, redo my acl/proxy stuff in the command line client and be >> merrily on my way? > > If you don't care about existing data, simple option would be to > delete the entire calendar imported into and create a new one. > > -- > Cyrus Daboo > > _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
