TID: Mystic BBS 1.12 A48   
   MSGID: 1:129/215 a63a1881   
   REPLY: 1:229/110 140f8145   
   TZUTC: -0400   
    SB> But, I also think that this might be a good idea, for when PiBBS is too   
    SB> busy grinding her nightly maintenance...after all, there are other   
    SB> reasons why a particular BBS might be busy...   
      
   Agreed that this type of BUSY event would be pretty useful if you want to   
   fully automate some things that require you to take the servers down.   
      
   I was experimenting with something like this before but what I struggled with   
   was exactly how I should handle existing connections to those servers.    
   Handling new connections during a defined maint window shouldn't be too hard   
   but figuring out the existing connections is a little more tricky.   
      
   ... Everyone has a photographic memory. Some don't have film.   
      
   --- Mystic BBS v1.12 A48 2022/04/03 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 616 123/10   
   SEEN-BY: 123/120 131 129/215 305 330 331 153/7715 154/10 30 40 50   
   SEEN-BY: 154/700 203/0 218/700 840 220/70 90 221/6 226/17 18 30 100   
   SEEN-BY: 227/114 201 229/110 206 307 310 317 400 424 426 428 452 550   
   SEEN-BY: 229/664 700 240/5832 250/5 8 266/512 267/800 280/464 282/1038   
   SEEN-BY: 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 633/280 712/848 770/1 2320/105 3634/12   
   PATH: 129/215 154/10 770/1 317/3 229/426