Subj : Synology Docker Mystic Test
To   : opicron
From : opicron
Date : Tue Feb 18 2025 09:20 pm

On Mon, Feb 17 2025 16:37:26 -0600, you wrote:

 op>  Ac>  > My first thought is that this is some bot/connection which tries t
 op>  Ac>  > connect unconventionally. Triggering something in Mystic which run
 op>  Ac>  > up the cpu for a minute or two.

So, after a lot of testing, debugging and trying to be on time to see what
is happening during these spikes.

It only happens when a telnet session is connecting to Mystic. The status of
the node is: 'Logging in' for those 1:30-2:30 minutes at 99% CPU usage.

In the startup.mps script I added a MenuCMD function call to set the Node 
status to something else when my custom login prompt shows. Which means the
cpu spike is happening before startup.mps is called. Which could be BEFORE 
or AFTER the Termtype detection.

I cannot set detect to ANSI only to solve this issue, because then we lost 
widescreen auto-support in Syncterm and Netrunner. And my board relies heavily
on regular or widescreen support, depending on what is detected.

Now that I know this I will set the Node status in connect.mps to see if it
is before or after detection to maybe help g00r00 in figuring out what
might be happening.

oP!

.... Hell hath no fury like the lawyer of a woman scorned.

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

.