Re: Re: Summer time.. binkd crashed ... again
  By: Wilfred van Velzen to Michiel van der Vlist on Mon Apr 06 2015 18:38:21

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

I run Vista.

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

Here is the log snippet you requested.  Remember that this is from the original
compile, which I no longer use.  I now use the same version as Michiel and Bill

+ 08 Mar 03:00:06 [3456] binkd.cfg changed!
+ 08 Mar 03:00:06 [3456] binkd.txt changed!
+ 08 Mar 03:00:06 [3456] more.txt changed!
+ 08 Mar 03:00:06 [3456] Reloading configuration...
- 08 Mar 03:00:07 [3456] servmgr listen on *:24554
  08 Mar 03:00:33 [4676] previous config is no longer in use, unloading

  08 Mar 10:27:56 [4652] BEGIN standalone, binkd/1.1a-68/Win32 -C binkd.cfg
  08 Mar 10:27:56 [4652] servmgr started
- 08 Mar 10:27:56 [4652] servmgr listen on *:24554
  08 Mar 10:27:56 [5504] clientmgr started

The blank line is in the log file.  You will notice at what time I noticed that
it had stopped, and restarted it 
--- SBBSecho 2.27-Win32