REPLY: 2:280/5555 61e96417   
   MSGID: 1:3634/12.73 61e96dc7   
   PID: GED+LNX 1.1.5-b20180707   
   CHRS: CP437 2   
   TZUTC: -0500   
   TID: hpt/lnx 1.9.0-cur 17-02-17   
    On 2022 Jan 20 14:18:08, you wrote to me:   
      
    MV> In an attempt to provoke the crashes I created an empty include file for   
   my   
    MV> binkd config file. With the Windows task manager I created an event that   
    MV> touched the date/time stamp of this empy file every five minutes. The   
    MV> rescan delay for my binkd is set to 60.   
      
   i remember you posting about this... it is one of the things that lead to me   
   attempting to reproduce the defect here on my OS/2 setup at that time... now   
   i'm on linux and the defect still exists...   
      
    MV> This was about five years ago. I let it run for a month or so. Binkd   
    MV> reloaded its config every 5 minutes and that did not cause a crash.   
      
    MV> So I thought "hmmm this version of binkd seems to have fixed the   
    MV> problem". But alas when I made changes in the actual config files the   
    MV> crashes reappeared. So it looks like it is not just the reloading the   
    MV> config files as such, some of the config files must actually change to   
    MV> make it crash.   
      
    MV> I gave up and stopped using the -C option.   
      
   i've continued to use it but have always stopped my binkd manually before   
   making and saving edits... at this time, though, i wanted to test for this   
   defect specifically because i had been talking with some other operators about   
   binkd and had noted that it can automatically reload its configs when changes   
   have been made to them... since i had not been seeing crashes every day when   
   my fidonet.binkd.txt nodelist is updated, i wondered about updating the other   
   config files and if things were working there... as it happens, i triggered   
   the defect and here we are with this current thread about it...   
      
   i must say that i find it quite strange that updating the contents of one   
   included file will trigger the defect but updating another included file isn't   
   even noticed at all...   
      
    MV> I did not formally document it at the time, so I am relying om memory.   
      
   my memory of your original posting appears to match what you write here :)   
      
   )\/(ark   
      
   "The soul of a small kitten in the body of a mighty dragon. Look on my   
   majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a   
   shiny thing!"   
   ... Margarine? I only use it recreationally. I wouldn't eat it!   
   ---   
    * Origin:  (1:3634/12.73)   
   SEEN-BY: 1/120 123 15/0 18/0 90/1 105/81 106/201 114/709 116/116 120/340   
   SEEN-BY: 123/0 25 40 115 126 131 180 190 200 755 129/305 330 135/300   
   SEEN-BY: 138/146 153/7715 154/10 222/2 226/30 227/114 229/110 200   
   SEEN-BY: 229/307 317 424 426 550 664 700 240/1120 5832 249/206 250/1   
   SEEN-BY: 266/512 275/100 1000 282/1038 292/854 299/6 300/4 301/1 317/3   
   SEEN-BY: 320/219 322/757 342/11 200 396/45 633/280 640/1321 1384 712/848   
   SEEN-BY: 3634/0 12 15 27 50 119   
   PATH: 3634/12 153/7715 229/426