TID: Mystic BBS 1.12 A46   
   MSGID: 1:153/7083 6195f914   
   CHRS: CP437 2   
   TZUTC: 0800   
      
   Hi,   
      
   I've toggled the "No Timeout" setting for my account (Mystic v1.12 A45   
   2020/08/26 (Linux/32)); but after sometime, the BBS would just boot me back   
   out (if I was telnet'd) or back to the bash prompt (if I just use 'mystic   
   -l').  I don't see any errors in the node?.log.   
      
   I haven't timed how long before it boots me; but I thought that the setting   
   would prevent this.   
      
   That said, the way it booted me looks like somehow the BBS crashed (but it   
   didn't as there aren't any errors showing).   
      
   If "No timeout" is set to true, wouldn't 1) The time on the top right stay the   
   same?  2) If the timeout was in effect, wouldn't a message saying (along the   
   lines of) "Sorry, you have used up all your time"?   
      
   I have my time set to 9999.   
      
   Any information appreciated.   
      
   Edmund   
      
      
      
      
   Edmund   
      
      
   ... An efficient bureaucracy is the greatest threat to liberty.   
   --- GoldED+/LNX 1.1.5-b20180707   
    * Origin: Eagle's BBS | HK (1:153/7083)   
   SEEN-BY: 1/123 30/0 80/1 90/1 103/705 105/81 120/340 123/131 129/305   
   SEEN-BY: 134/100 153/0 105 757 7083 154/10 218/700 840 221/1 6 226/30   
   SEEN-BY: 227/114 702 229/424 426 428 452 550 664 700 981 240/1120   
   SEEN-BY: 240/5832 249/206 307 317 400 261/38 280/464 282/464 1038   
   SEEN-BY: 292/854 301/0 1 101 113 317/3 322/757 335/364 341/66 342/200   
   SEEN-BY: 633/280 712/848 920/1 4500/1 5020/1042 5058/104   
   PATH: 153/7083 757 221/6 301/1 229/426