TZUTC: -0800   
   MSGID: 58796.sync_sys@1:103/705 2d6f360b   
   PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0   
   TID: SBBSecho 3.30-Linux master/3b5271993 Oct 31 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: UTF-8 4   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/issues/998#note_7831   
      
   It's *a* solution, but it's a much bigger hammer than is needed for the   
   purpose... the maintenance for any specific door doesn't require that nobody   
   be logged onto any node on the BBS, it only requires that nobody be running   
   that one specific copy of that one door.   
      
   Kicking everyone off the BBS just in case one of them is thinking about   
   running a specific door seems a bit excessive.   
   --- SBBSecho 3.30-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 13 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 601 610 700 840   
   SEEN-BY: 218/860 880 226/30 227/114 229/110 112 206 317 400 426 428   
   SEEN-BY: 229/470 700 705 266/512 280/464 291/111 301/1 320/219 322/757   
   SEEN-BY: 342/200 396/45 460/58 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426