Hello Michiel,

> On Monday March 30 2015 21:15, you wrote to andrew clarke:

>>> I wonder if the crash is caused by the way the old config file is
>>> unloaded from memory.

>> what "old config"??? the only thing that changed was the system's
>> time... it jumped forward or backward one hour... there was no other
>> change on the system...

>Binkd crashes when the config is changed. Or... when it "thinks" the config ha
> changed because of the time jump. It reports a change of config.

> + 29 Mar 01:55:04 [11644] done (from 3:633/267@fidonet, OK, S/R: 0/0 (0/0
> bytes))
> 29 Mar 01:55:04 [11644] session closed, quitting...
> + 29 Mar 03:00:01 [19756] binkd.cfg changed!
> + 29 Mar 03:00:01 [19756] d:\fido\binkd\nodes.cfg changed!
> + 29 Mar 03:00:01 [19756] Reloading configuration...
> - 29 Mar 03:00:01 [19756] servmgr listen on *:24554


My system didn't report a config change:

    08 Mar 01:34:05 [30690] Creating toss-now
    08 Mar 01:34:05 [3347] rc(30690)=0
    - 08 Mar 03:00:32 [3347] incoming from 196-38-245-190.fibertel.com.ar

No config change noted, just the time stamp in the log changed. This is the
linux version as below:

Binkd 1.0a-396 (Oct  3 2010 02:31:53/Linux) Compilation flags: gcc, zlib,
bzlib2.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2