TZUTC: -0800   
   MSGID: 56703.sync_sys@1:103/705 2b9330cf   
   PID: Synchronet 3.20a-Linux master/9d3a8113d Nov 04 202 GCC 12.2.0   
   TID: SBBSecho 3.21-Linux master/8aea7d593 Nov 06 2024 00:24 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/issues/661#note_5929   
      
   I've seen this happen a couple of times recently (again on git.synchro.net)   
   where my FIDOIN timed event configured to run in the Background did this same   
   thing: hung the event thread, but never actually executed.   
      
   Again, the `Detaching external process` log message was conspicuously absent.   
      
   Also interesting, a restart of the sbbs service appears to gracefully shutdown   
   the bbs_thread, which waits (forever) for the event_thread() to terminate, and   
   it does. So if external() is indefinitely blocked in this scenario (as it   
   appears), it gets unblocked when bbs_thread() is terminated (or recycled? I   
   should try that too).   
      
   I've added a bunch of debug-level log messages to external() to hopefully   
   narrow down the point of blockage if/when this happens again.   
   --- SBBSecho 3.21-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 128/187 153/757 7715   
   SEEN-BY: 154/10 30 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426