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

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

 MvdV> Yes, there is no tzoff configured in my setup.

   Maybe there should be?

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

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

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

   Sounds more suspicious than what Argus is doing.

   Alas, as I said, I don't consider this a major problem. I've been running Argus for more than ten years now, and I have never seen any tzutc problems with it.

   But if you can make a poll, and make sure you remember your local time, and then check your log file, I'll place the issue in the "very strange bugs, that nobody knows how to correct" folder here, and then I'll take it from there. 8-)

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
 * Origin: news://felten.yi.org (2:203/2)

.