RE: Setup Problem for SyncCM

["Bharat Mediratta" <bmedirat@xxxxxxxxxxxxxx>]

Hey guys --

Yea, I remember writing that :-)

That particular piece of code is simply doing a sanity check
to make sure that it won't have problems with your calendar
later on during the sync.  It's possible, if somebody is motivated
to change the code, to make it such that instead of failing it
brings up a dialog and asks you if you want to continue.  It's
entirely possible that you don't have permissions to examine
the calendar's attributes (ie, you're not the owner) but you
still have read/write privileges (e.g., you're the admin for
your boss' calendar, etc.)

-Bharat

-----Original Message-----
From: owner-pilotmgr@xxxxxxxxxxxxxxxxxxxx
[mailto:owner-pilotmgr@xxxxxxxxxxxxxxxxxxxx]On Behalf Of Alan Harder
Sent: Tuesday, December 15, 1998 5:05 PM
To: johnh@xxxxxxxxxxxxxxxxxxx
Cc: pilotmgr@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: Setup Problem for SyncCM


> You do not have authority to examine the attributes for 
> johnh@nosun.  Without examining the calendar's attributes, it is
> impossible to tell whether or not it will work with SyncCM.

Here is some info I dug up.. hope it helps:

------------- Begin included message ---------------
Before SyncCM does anything with
your calendar, it first checks to see what permissions it has
by reading the calendar attributes.  However, if you do not
have owner permission, it cannot do some of the operations that
it needs to do to update the file.  Annoyingly enough, you
cannot bestow ownership priveleges through the CDE gui, you
have to do it by editing the file.  Here's how you do it
(this is from memory, I haven't done this in at least 3 months
so take it with a grain of salt).

If you're adding yourself to a calendar called "foo" then
1.	edit /var/spool/calendar/callog.foo (make a backup first)
2.	Around line 4 is an Access List line with a series of
	"name: number" pairs.  The number for "foo" would be
	~33000.  Copy that number to the pair containing your
	name so both you and "foo" have the same access.
3.	kill rpc.cmsd

It should work after that.  Good luck.

-----------------------------------------------

	- Alan
------------------------------------------------------------------------
***********************************************************
*             This is a public mailing list!              *
* Please do not publish Sun proprietary information here! *
*        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
*             http://www.moshpit.org/pilotmgr             *
***********************************************************