= Сообщение: 483 из 7442 ============================================== IPV6 = От : Michiel van der Vlist 2:280/5555 19 Mar 14 23:29:10 Кому : Björn Felten 19 Mar 14 23:29:10 Тема : Time warp? FGHI : area://IPV6?msgid=2:280/5555+532a1ac8 На : area://IPV6?msgid=2:203/2+532a10fe = Кодировка сообщения определена как: CP850 ================================== Ответ: area://IPV6?msgid=2:203/2+532a20f8 ============================================================================== 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
