home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!utcsri!bonnie.concordia.ca!hobbit.ireq.hydro.qc.ca!NetNews.ireq.hydro.qc.ca!gamin
- From: gamin@ireq-robot.hydro.qc.ca (Martin Boyer)
- Newsgroups: comp.sys.sun.apps
- Subject: Re: My Sun calendar man. went flaky - why?
- Message-ID: <GAMIN.92Sep13112450@amadeus.ireq-robot.hydro.qc.ca>
- Date: 13 Sep 92 15:24:50 GMT
- References: <1992Sep9.222549.29805@athena.cs.uga.edu>
- Sender: news@ireq.hydro.qc.ca (Netnews Admin)
- Organization: Le laboratoire de robotique de l'Institut de recherche
- d'Hydro-Quebec
- Lines: 50
- In-Reply-To: weinri@athena.cs.uga.edu's message of 9 Sep 92 22:25:49 GMT
-
- >>>>> Kevin Weinrich writes:
-
- >when I double-click on a day, it brings up the *previous*
- >day. If I set an appointment, it schedules it for a different time
- >(this last time, I set it for 6 p.m., it showed up at 1 p.m.).
-
- That's a bug in cm. Here's an excerpt from a message I saved a while
- ago:
-
- >From: guy@Auspex.COM (Guy Harris)
- >Newsgroups: comp.windows.open-look
- >Subject: Re: SUN Calendar Manager
- >Date: 22 Apr 92 23:59:53 GMT
- >Organization: Auspex Systems, Santa Clara
- >
- >>after all, it no longer
- >>stupidly requires the kernel's notion of the time zone to be set, as of
- >>OW 3.0, as far as I know.)
- >
- > To have made it depend on the kernel's notion of the time zone
- > in one release is a misfortune; to have done it in two releases
- > seems more like carelessness.
- >
- > -- not Lady Bracknell (with apologies to Oscar
- > Wilde)
- >
- >Well, I guess I was wrong. Somebody in "comp.sys.sun.apps" said that
- >the OW 3.0 CM didn't work right until they ran "tzsetup". I tried it
- >out by running a small program to set the kernel's notion of the current
- >time zone to a GMT offset of 0, and a DST type of DST_NONE, *without*
- >changing the *system's* notion of the current time zone (i.e.,
- >"/usr/share/lib/zoneinfo" still pointed to
- >"/usr/share/lib/zoneinfo/US/Pacific"), and fired up the OW 3.0 "cm"
- >(which then fired up "rpc.cmsd", which wasn't running prior to that).
- >
- >Surprise surprise, it was massively confused, but when I killed 'em both
- >off, ran "tzsetup", and re-started "cm", it was happier.
-
- The problem, then, is that cm uses antiquated function calls.
- The work-around is to run tzsetup to tell your kernel to support those
- function calls.
-
- On a broader scale, the problem is with Sun's software quality
- assurance.
-
- --
- 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
-