From: gamin@ireq-robot.hydro.qc.ca (Martin Boyer)
Newsgroups: comp.windows.x.apps,comp.sys.sun.apps
Subject: Re: Calendar Manager in OW3
Date: 27 Aug 92 01:38:49 GMT
Distribution: usa
Organization: Le laboratoire de robotique de l'Institut de recherche
	d'Hydro-Quebec

>>>>> barbara.tongue  writes:

>we're wondering the best way to set up the system - ie, have each person's
>indiviudal callog.$LOGNAME on their workstation or remotely mount
>/spool/calendar from the server.

We've been using this for several months without problems:
(Follow the instructions PRECISELY)

----------------------------------------------------------------------
From: matthew@sunpix.East.Sun.COM (Matthew Stier - Sun Video and Imaging Products)
Newsgroups: comp.windows.open-look
Subject: Re: Calendar Manager, /var/spool/calendar ownership problems
Date: 22 Jan 92 16:30:11 GMT
Organization: Sun Microsystems, Research Triangle Park, NC

In article <1992@fang.dsto.oz> wjm@itd.dsto.oz.au (Wayne Mildren) writes:
>vdp@mayo.edu (Vinayak Dutt, Graduate Student (Biophysics)) writes:
>
>
>>I am  having problems in running calendar manager on our network
>>of suns. everytime i start the calendar manager, rpc.csmd 
>>complains that /var/spool/calendar is not owned by daemon and
>>its dies out.
>
>We have the same problem. We also have the calendar directory on a central
>fileserver.
>The only solution I can find is to give each Sun root access to this directory
>via the /etc/exports file on the fileserver. This can be tedious - in our
>case we have 70+ Suns and the /etc/exports file doesn't accept a netgroup
>for root access.

This is the solution we use at our site (sunpix.east.sun.com).

After having a few disk SparcStation local disk crash after a power outage.
Our sysadm decided to provide a way to backup calendars, in the same manner
he was backing up mail. [note: this works for OW 3.0.  OW 2.0 is untested]

1) Create the '/var/spool/calendar' directory on the machine that will be the
   cm host (hence forth know as 'cmhost').

2) Foreach user, have the users complete all changes in progress.

3) Have each user bring up the properties editor (Edit -> Properties).

4) Under "Catagory:", select 'Display Settings'.  
   For 'Default Calendar", enter "user@cmhost" and (Apply) the changes. 
   [of course "user" is the users name, and cmhost is the host that the
    calendars will be placed on.]

   For me, I entered 'matthew@sunpix'.

5) Under "Catagory:", select 'Access List and Permissions'.
   Next to the (Calendar) button, enter the user's name.
   For Permissions, select the Browse, Insert, and Delete buttons.
   Now press the (Calendar) and (Apply) buttons.  
   This will give the user all Browse, Insert, and Delete permissions.

   For me, I entered "matthew" on the line next to the (Calendar) button, 
   and then pressed Browse, Insert, Delete, Calendar, and Apply.

6) Quit the calendar manager.

7) Copy the calendar to the cmhost.
   [rcp /var/spool/calendar/callog.$USER cmhost:/var/spool/calendar]

8) Ensure that the permissions on the new file are correct.
   [rsh cmhost "chmod 460 /var/spool/calendar/callog.$USER"]

9) Have the user start and use a new calendar manager.

10) Instruct the user to ignore the "user@hostname" entry under the 
   (Browse) button.

-- 
Matthew Lee Stier                          |
Sun Microsystems ---  RTP, NC  27709-3447  |     "Wisconsin   Escapee"
Email: matthew.stier@East.Sun.COM          |
Phone: (919) 469-8300 fax: (919) 460-8355  | 
----------------------------------------------------------------------

--
Martin Boyer                            mboyer@ireq-robot.hydro.qc.ca
Institut de recherche d'Hydro-Quebec    mboyer@ireq-robot.uucp
Varennes, QC, Canada   J3X 1S1
+1 514 652-8412
Xref: sparky comp.windows.x.apps:905 comp.groupware:742