Re: [IM-Talk] InterMapper died with DST

Mon, 04 Apr 2005 09:19:18 -0700

Brief update. I later changed my TZ to MST, Arizona's yearround TZ (they don't observe DST), and that did not crash InterMapper. And MST is convenient for our particular situation, because we're in PDT, and PDT == MST == -0700 . So now the time is "correct", even though our TZ is wrong, but that is a relatively minor concern for us, and we can certainly operate in that mode until there is a fix.

        -J-



----------------------------------------------------------------------

Subject: Re: [IM-Talk] InterMapper died with DST
From: "Richard E. Brown" <[EMAIL PROTECTED]>
Date: 03 Apr 2005 11:57:46 EDT

Jason:

Yikes! We haven't heard anything like this, but that's a pretty specific error
message, and the timing is plenty suspicious.

I have submitted your note as a bug report. Thanks for your patience.

Rich Brown                    [EMAIL PROTECTED]
Dartware, LLC                 http://www.dartware.com
10 Buck Road, PO Box 130      Telephone: 603-643-2268
Hanover, NH 03755-0130 USA    Fax: 603-643-2289

--- Jason K.Werner wrote:
The instant we went forward an hour, InterMapper 4.2.4 (OS X Server
10.3.8) died:

Apr 3 03:00:00 presidio intermapperd[707]:
ASSERT#UNIX#4.2.4#IsSupportedDateTimeValue(itsUnixTime)#XDateTime_Unix. c
pp#97#Darwin/7.8.0#Ex61#As1#
Apr 3 03:00:05 presidio intermapperd[707]: ExitProcess with status 1.
XBugReport

Attempted restart, failed with same error.  Upgraded to 4.2.5 just for
kicks, same result.

I'm in Pacific TZ, PST/PDT.  Changed TZ to GMT, and intermapperd was
happy with that.  Experimented with various timezones (Chicago, etc.),
none worked.  Sticking with GMT for now.

Curious if anyone else is seeing this.
--- end of quote ---


____________________________________________________________________
List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

Reply via email to