Re: bug in timezone???

[Mike Kupfer <Mike.Kupfer@eng>]

> Honestly, I keep asking: what about the message is unclear?

Well, since you ask :-), there are a couple things that bother me about
the message and the FAQ text.

1. There's no technical explanation of the bug, just a bald assertion
that it's an OS bug and not a PilotManager bug.  Okay, if that's
really the case, why hasn't this been fixed yet in Solaris and
whatever OS's provoke the message?  Heck, why can't I even find a bug
for this in the Sun bug database?

2. The recommended "fix" is to use a timezone like PST8PDT instead of
US/Pacific.  Why on Earth does this matter?  On my Solaris 2.6 box
/usr/share/lib/zoneinfo/PST8PDT and /usr/share/lib/zoneinfo/US/Pacific
are hard links to each other, yet US/Pacific provoked a complaint when
I first installed PilotManager, but PST8PDT did not.

So the bottom line is, yes, the message and FAQ are very clear about
what to do to make the message go away.  On the other hand, the two
issues I mentioned above lead me to wonder if things are as simple as
the message and FAQ assert.  So I'm not at all surprised to see that
people continue to post queries about this problem.

mike
--
Mike Kupfer				kupfer@xxxxxxxxxxx
NFS Engineering				Speaking for myself, not for Sun.
------------------------------------------------------------------------
***********************************************************
*             This is a public mailing list!              *
* Please do not publish Sun proprietary information here! *
*        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
*             http://www.moshpit.org/pilotmgr             *
***********************************************************