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
Hi tack,
--On June 23, 2008 12:09:26 PM -0700 tack <[EMAIL PROTECTED]> wrote:
> Thanks Cyrus.
>
> Would I do this by rm/mkdir in the client tool or something similar?
> I couldn't find where this was on the regular command line.
Simple option is to just delete the file on disk and restart the ca
Thanks Cyrus.
Would I do this by rm/mkdir in the client tool or something similar?
I couldn't find where this was on the regular command line.
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:
>
>
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
Hey everybody
We migrated people to our DCS implementation and ran into an issue
where some people's calendars were accessible as subscriptions just
fine, but others you could authenticate (authenticated:read ACL) but
it just timed out.
We had advised people to migrate their old calendars o
