[Thread Prev][Thread Next][Thread Index]

RE: Timezone Conflict



NO! 
NO NO NO!

Can I possibly be more emphatic!  Do NOT comment out that line
of code, it's there for a reason.  

What is happening here is that PilotManager is protecting you from
a bug in the Solaris 2.5.1/2.6 operating systems.  These OS' have 
a bug which makes it calculate the time incorrectly in certain 
timezones.  What happens is the localtime(0) call does not account 
for DST properly and the time it calculates is off by 1 hour.  Since
very few apps use localtime(0) for their base calculations, this 
doesn't show up very often.  When PilotManager starts up, it checks
your OS to see if you have the bug and will not let you sync if you
have it, so that it won't break your calendar.  However, if you 
short-circuit PilotManager into working anyway, you're going to 
definitely cause damage to your calendar.

There are two ways to fix this.  If you make your timezone explicit
(ie, change it from "US/Pacific" to "PST8PDT" this problem. 
Otherwise, if you install the patch, everything will work as it 
did before (well, for SyncCM -- Alan can you verify this for 
SyncTime?). SyncCM will take into account your new timezone and 
will NOT rearrange your Pilot appointments.

Alas, I no longer have access to the patch database so somebody
else will have to look up the info for this patch...

-Bharat

> -----Original Message-----
> From: Gunnar Stahl - Sun Sweden - Snr IR Business Advisor NEEUR
> [mailto:Gunnar.Stahl@xxxxxxxxxxxxxx]
> Sent: Monday, March 30, 1998 6:22 AM
> To: Elias.Martenson@xxxxxxxxxxxxxx
> Cc: owner-pilotmgr@xxxxxxxxxxxxxxxxxxxxx;
> Christoph.Boehm@xxxxxxxxxxxxxxx; pilotmgr@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: Timezone Conflict
> 
> 
> This obviously hits only some people for unknow reasons.
> 
> I have found a way to correct this, but until hearing more 
> from the "author"
> I suggest it is treated as a work-around, even if no negative 
> side-effect
> have been noticed.
> 
> In PilotManager 1.105, line 2342 a subroutine called 
> checkTimeBug starts.
> If you "shortcut" the return statement on line 2348 by replacing the
> current return with 'return (0);' PilotManager will work.
> 
> As I said. I don't know the sideeffects even if I haven't 
> noticed any problems
> on the machines I tried with.
> 
> 
> Best regards
> 
> /Gunnar Ståhl
> --------------------------------------------------------------
> ----------
> ***********************************************************
> *             This is a public mailing list!              *
> * Please do not publish Sun proprietary information here! *
> *        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
> *             http://www.moshpit.org/pilotmgr             *
> ***********************************************************
> 
------------------------------------------------------------------------
***********************************************************
*             This is a public mailing list!              *
* Please do not publish Sun proprietary information here! *
*        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
*             http://www.moshpit.org/pilotmgr             *
***********************************************************


SourceForge.net Logo