TZUTC: -0700   
   MSGID: 52008.syncprog@1:103/705 2c46b282   
   PID: Synchronet 3.20e-Linux master/ad9ab307f Mar 18 2025 GCC 12.2.0   
   TID: SBBSecho 3.24-Linux master/ad9ab307f Mar 18 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/commit/0ac5ed5728c53d93eb347c23   
   Modified Files:   
   	src/sbbs3/main.cpp   
   Log Message:   
   Set node "interrupt" flag to try to gracefully disconnect user blocking event   
      
   When a timed event is configured to run "exclusively", all nodes need to not be   
   in in-use. As it was, after waiting 60 minutes for the online user(s) to   
   notice they'd run out of time and disconnect, we'd just (rather ungracefully)   
   close the sockets used by such node(s) connections. This results in same logged   
   errors about trying to send to bad socket descriptors and provides no feedback   
   to the user about why they were disconnected.   
      
   Since we have the node interrupt flag (which hopefully, all scripts are   
   checking via node_sync) - use that to try to more gracefully terminate the   
   user's session/connection after 30 minutes of waiting for the user to   
   disconnect.   
      
   If after 60 minutes of waiting, the node is still in-use, we still do the   
   socket disconnection method.   
   --- SBBSecho 3.24-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 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 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426