Subj : Time warp?
To   : Bj”rn Felten
From : Michiel van der Vlist
Date : Wed Mar 19 2014 23:29:10

Hello Bj”rn,

On Wednesday March 19 2014 22:49, you wrote to me:

 MvdV>> Now ask a few other how they see the time info that your system
 MvdV>> emits. Wilfred? Kees?

 BF>    Did you check your binkd.cfg as I suggested?

Yes, there is no tzoff configured in my setup.

 BF>    And no, I will not claim that it's *not* my system that's at fault
 BF> here. I don't even consider it a problem.

 BF>    But I *do* know from many years of programming experience, that
 BF> programs compiled with Microsoft products more often than not do not
 BF> handle international issues properly.

I am aware of those problems, but it is not relevant in this case:

Binlog and tzoff
Purpose: binlog keyword specifies full filename to the binary log file in T-Mail-compatible format.

 Most compilers under DOS-derived systems return local time as a value of time(). Even worse, this value is inconsistent from one compiler to another and from one library to another, so that it's quite possible that binkd and some T-Mail log analyser will be using different implementations of time() and output inconsistent timing.

tzoff keyword provides a workaround for this bug. You can specify an arbitrary time offset (in seconds) in order to force both programs to give same time values. This keyword affects time offset for binary logging only specified by binlog and/or fdinhist and fdouthist


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
 * Origin: 2001:470:1f15:1117::1 (2:280/5555)

.