Subj : Binkd 1.1a77 binaries for Win32, Win64, OS/2
To   : Michiel van der Vlist
From : Pavel Gulchouck
Date : Thu Jan 28 2016 04:59 pm

Hi Michiel!

25 Jan 16, Michiel van der Vlist ==> Pavel Gulchouck:

 MvdV>>> I have been proviking this version by changing te config files
 MvdV>>> every few minutes and so far it has not crashed.

 MvdV>>> Have you changed anything regarding this problem or is it
 MvdV>>> co‹ncidence?

 PG>> Yes, some code related to reloading config was changed, but I'm not
 PG>> sure was the problem in fact fixed or the bug is just hidden and will
 PG>> occure rarely.

 MvdV> It seems the bug is still there. binkd just crashed on me, two minutes 
after changing the config again. So, i can't give
 MvdV> you a postmortem report. I simply terminated itself, no error 
information.

Now I built linux multithread binkd version, started it on my node and with -C 
switch and touch config every 5 minutes.
2 days running - no errors. :-(

Could you please show binkd logs (as detailed as you have) before the crash?

And do you have "exec" parameters in binkd config? If yes, it's possible that 
listen socket inherited by executed external utility, then binkd reopen the 
socket on config reload, and cannot bind listen socket because it's "already in 
use".
Problem with socket inheritance described here:
http://stackoverflow.com/questions/12058911/can-tcp-socket-handles-be-set-not-inheritable
AFAIU it's possible to workaround by DuplicateHandle() and set "noinherit" 
attribute, but it's not easy to test it in binkd.

              Lucky carrier,
                           Pavel
                           aka  gul@gul.kiev.ua
--- GoldED+/LNX 1.1.5
 * Origin: II:CDLXIII/LXVIII (2:463/68)

.