Xref: utzoo alt.sys.sun:1687 comp.windows.news:2370 Path: utzoo!utgpu!cs.utexas.edu!uunet!snorkelwacker!apple!sun-barr!newstop!exodus!xebra.Eng.Sun.COM!nannette From: nannette@xebra.Eng.Sun.COM (Nannette Simpson) Newsgroups: alt.sys.sun,comp.windows.news Subject: Re: OW - Calendar Manager Message-ID: <1457@exodus.Eng.Sun.COM> Date: 17 Oct 90 18:37:22 GMT References: <13860@ulysses.att.com> Sender: news@exodus.Eng.Sun.COM Followup-To: alt.sys.sun Distribution: alt.sys.sun Organization: Sun Microsystems, Mt. View, Ca. Lines: 72 In article ks@tut.fi (Syst{ Kari) writes: > > >Today I discovered a new problem in Calendar Tool. > >My callog-files was overwitten last nigth (4am), and most of my appointments >were lost. This might have something to do to the fact that all our >computers share the same /var/spool/calendar. > >So, be warned, don't trust on calendar tool if you have o common NFS-mounted >/var/spool/calendar. > >PS. I would be glad to see the Sun's comment on the /var/spool/calendar issue ! > > > >-- >This article represents my personal views. >NeWS flash: "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 The problem is that there are separate daemon processes running on each machine that you've logged into, each mounting the same backing file (callog file): _________ _________ _________ A B C --------- --------- --------- rpc.cmsd rpc.cmsd rpc.cmsd | | | | | | _________________________________________ server: callog file _________________________________________ Every one of these daemons will wake up to garbage collect its data structure back into the callog file. It's a lot like vi- the last one "wins" and becomes the "truth." If you truly want to keep your calendar data in one location and travel from machine to machine, I recommend the following: 1. Mount the callog files onto your "primary" machine. 2. From your primary machine, give Browse, Insert & Delete access to yourself on the other machines. 3. When you're working on one of the other machines, Browse your calendar from that machine so that all transactions go through your primary machine. For instance: 1. I am "nannette@xebra." My callog file resides on my workstation, xebra. 2. From xebra, I give "nannette@foo, nannette@bar" all privileges to my calendar. 3. When I log into foo or bar, I can browse "nannette@xebra" and transact it just as if I were on my primary machine. Admittedly, this is cumbersome for those of you running in a primarly shared workstation environment. But this procedure will ensure that you will not lose data. Suggestions are always welcome. -- Nannette Simpson Internet: nannette@Eng.Sun.COM Sun Microsystems, Inc. UUCP: ...!sun!nannette 2550 Garcia Ave. MS 1-40 Phone: (415) 336-2969 Mountain View, CA 94043