TID: FMail-W32 2.1.3.7-B20170919   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: CP850 2   
   MSGID: 2:280/5555 61e96417   
   REPLY: 1:3634/12.73 61e95151   
   Hello mark,   
      
   Let me add my 2 cts.   
      
   In an attempt to provoke the crashes I created an empty include file for my   
   binkd config file. With the Windows task manager I created an event that   
   touched the date/time stamp of this empy file every five minutes. The rescan   
   delay for my binkd is set to 60.   
      
   This was about five years ago. I let it run for a month or so. Binkd reloaded   
   its config every 5 minutes and that did not cause a crash.   
      
   So I thought "hmmm this version of binkd seems to have fixed the problem". But   
   alas when I made changes in the actual config files the crashes reappeared. So   
   it looks like it is not just the reloading the config files as such, some of   
   the config files must actually change to make it crash.   
      
   I gave up and stopped using the -C option.   
      
   I did not formally document it at the time, so I am relying om memory.   
      
   Just my 2 cts.   
      
   Cheers, Michiel   
      
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: http://www.vlist.eu (2:280/5555)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 123/120 131 124/5016 129/305 330 153/250 757 7715 154/10   
   SEEN-BY: 203/0 218/840 220/70 221/0 6 226/17 30 227/114 229/110 200   
   SEEN-BY: 229/307 317 424 426 550 664 700 240/5832 249/206 250/5 8   
   SEEN-BY: 266/512 267/800 280/464 5003 5555 282/1038 292/854 8125 298/25   
   SEEN-BY: 301/1 305/3 310/31 317/3 320/219 322/757 341/234 342/200   
   SEEN-BY: 396/45 423/120 460/58 633/280 712/848 770/1 100 340 772/210   
   SEEN-BY: 772/220 230 2452/250 5019/40 5020/1042 5053/58   
   PATH: 280/5555 464 770/1 317/3 229/426