Subj : Re: Synology Docker Mystic Test
To   : fusion
From : opicron
Date : Wed Feb 12 2025 06:54 pm

 fu> On 10 Feb 2025, Accession said the following...
 fu>  
 fu>  Ac> On Mon, Feb 10 2025 22:54:46 -0600, you wrote:
 fu>  Ac> 
 fu>  Ac>  > right on :) yeah just kinda sucks to see mystic in limbo needing
 fu>  Ac>  > workarounds..
 fu>  Ac> 
 fu>  Ac> Pretty sure if you force ANSI instead of using detection, it does
 fu>  Ac> basically the same thing as your MPL script does without any
 fu>  Ac> "workarounds."
 fu> 
 fu> the "workarounds" here were referring to MIS getting into a state it won't
 fu> accept connections, requiring his script to restart the docker image.
Yes this is correct. 

 fu> somewhere between the bot being allowed to connect, dumping whatever it do
 fu> the mystic login prompt, and then getting booted for incorrect passwords o
 fu> idle timeout, is causing MIS or mystic to mark the node BUSY permanently, 
 fu> other issues.
Again correct, the constant hammering does 'something' which causesm mystic to
be unresponsive. Of course it could be the server too, but I did not change
anything except mystic version.

 fu> that's the only problem. it doesn't really matter whether or how we boot t
 fu> user for not having ANSI. what if i want to allow non-ANSI users? sync doe
 fu> mystic does too, but the bots are breaking the server.. it's a bug ;)
And who needs ascii anyway, all scripts I write are full of nice ansi stuff. 
So its a win to boot connections when they detect ascii and to do it at
the connect.mps script.

For now, I have been following your advice, and I do not see mystic become
unresponsive anymore. Thanks for making me work for it ^^

oP!

.... We come in peace.  Shoot to kill.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: TheForze - bbs.theforze.eu:23 (21:3/126)

.