Hi,

On 2015-04-06 18:00:07, Michiel van der Vlist wrote to andrew clarke:
  about: "Summer time.. binkd crashed ... again":

 MV>>> The clock jumps from 02:00 to 03:00. Summer time! Binkd thinks
 MV>>> that the config files have changed and reloads its config. So far
 MV>>> so good. (or not, depending..)

 ac>> I can reliably get the same build of BinkD to reload its configs
 ac>> whenever I change timezones under Windows 7. I think that's a bug.

 MvdV> I too would call it a bug, but in itself it is a pretty harmless one. If
 MvdV> only binkd did not crash on reloading the config... :-(

That's the important thing to focus on: It shouldn't crash!

 ac>> But I can't get it to crash after the config change. I'm thinking
 ac>> there may be something in your binkd configs that's triggering it.

 MvdV> Or maybe it is OS specific. I still run XP. I could do a test on my
 MvdV> laptop,. That has Win7.

It is, or to be more exact filesystem specific. The code that reads the file
time in binkd is very generic, there aren't different versions for any OS. It
uses the stat() function to read the file time, which is returned as a time_t
value which is supposed to contain the file time in a timezone independent
form. But if the filesystem stores the file time in local time, and the
timezone or dst changes, the conversion to utc (in time_t format) returns a
different value, and binkd thinks the file time changed...

Bye, Wilfred.


--- FMail-W32-1.69.4.102-B20150403