Subj : Re: No Timeout setting
To   : Edmund Wong
From : g00r00
Date : Thu Nov 18 2021 12:00 pm

 EW> I've toggled the "No Timeout" setting for my account (Mystic v1.12 A45
 EW> 2020/08/26 (Linux/32)); but after sometime, the BBS would just boot me
 EW> back out (if I was telnet'd) or back to the bash prompt (if I just use
 EW> 'mystic -l').  I don't see any errors in the node?.log.

The No timeout flag disables the inactivity timeout (not time per day) but there are some many possiblities as to why you might be getting disconnected, anything from a bug to running out of time, to your ISP/router killing open sockets because you're idle and it thinks they're stale (ie you would need a
telnet client if connected via telnet that sends NOOP to stay connected)...

If you are connected via ./mystic -l and it happens, that seems to point to something else not client/router related.  If you ran out of time (ie minutes per day) or were removed from inactivity, then it should have printed a message or logged you out as you noted.

I don't really have a good explaination for you at the moment to be honest.

.... Help! I can't find the "ANY" key.

--- Mystic BBS v1.12 A47 2021/11/06 (Windows/32)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.