Subj : Re: Synology Docker Mystic Test
To   : Accession
From : fusion
Date : Tue Feb 11 2025 07:43 pm

On 10 Feb 2025, Accession said the following...
 
 Ac> On Mon, Feb 10 2025 22:54:46 -0600, you wrote:
 Ac> 
 Ac>  > right on :) yeah just kinda sucks to see mystic in limbo needing
 Ac>  > workarounds..
 Ac> 
 Ac> Pretty sure if you force ANSI instead of using detection, it does
 Ac> basically the same thing as your MPL script does without any
 Ac> "workarounds."

the "workarounds" here were referring to MIS getting into a state it won't accept connections, requiring his script to restart the docker image.

somewhere between the bot being allowed to connect, dumping whatever it does at the mystic login prompt, and then getting booted for incorrect passwords or idle timeout, is causing MIS or mystic to mark the node BUSY permanently, among other issues.

that's the only problem. it doesn't really matter whether or how we boot the user for not having ANSI. what if i want to allow non-ANSI users? sync does.. mystic does too, but the bots are breaking the server.. it's a bug ;)

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
 * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)

.