Xref: utzoo alt.sys.sun:1634 comp.windows.news:2350 Path: utzoo!attcan!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!zaphod.mps.ohio-state.edu!rpi!uwm.edu!bionet!snorkelwacker!bloom-beacon!eru!hagbard!sunic!news.funet.fi!tut!ks From: ks@tut.fi (Syst{ Kari) Newsgroups: alt.sys.sun,comp.windows.news Subject: Re: OW - Calendar Manager Message-ID: Date: 9 Oct 90 12:58:11 GMT References: Sender: news@funet.fi (#News ) Distribution: alt.sys.sun Organization: Tampere Univ. of Technology, Finland. Lines: 35 In-Reply-To: fitz@frc2.frc.ri.cmu.edu's message of 30 Sep 90 20:28:41 GMT In article fitz@frc2.frc.ri.cmu.edu (Kerien Fitzpatrick) writes: > How are others handling the way that the Calendar Manager wants to > write files to /var/spool/calendar on whatever host you are currently > logged in to? Are people mounting via NFS? Good points/bad points? I've now used a common /var/spool/calendar for a week ot two. Today I found two problems: 1) The client (rpc.cmsd actually) seems to need a root access to the filesystem containing /var/spool/calendar. 2) Today we tested the browsing of other user's calendar and permissions. After that by OWN two calendar-tools on different hosts seem to have a different view to my calendar. The one running on file-server sees only the entries added today. ls-command on both sides tells that the callog-files have equal size, so it is not a NFS-problem. The file is the same for both hosts, but the deamons have different behaviours. BTW: Both hosts do have the root access. Any ideas ? Currently, I thing that the best solution is to run calendar-managers only on one host. The user should change his/her root-menu so that cm is started automatically on the desired host. -- This article represents my personal views. Quote of the year: "X is the Fortran of windowing systems." Kari Systa, Tampere Univ. Technology, Box 527, 33101 Tampere, Finland work: +358 31 162585 fax: +358 31 162913 home: +358 31 177412