Subj : Synology Docker Mystic Test
To   : opicron
From : Accession
Date : Mon Feb 17 2025 02:26 pm

Hey opicron!

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

 > When I run ./mystic -T+ myself it just starts a local board node. I
 > guess its the command to open a telnet session when someone connects.

I believe the command is './mystic -T#' where "#" is a time in minutes that whoever logging in would be limited to (even if their user account is set to something higher). If something is running './mystic -T+' then you've really lost me, since that doesn't seem to be a valid parameter for that command, at all.

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

I'm pretty stumped on this one, to say the least. The _only_ way I can get 'top -c' to produce that command is if I manually type './mystic -T20' or something similar at the Linux console prompt (which means I'm actually forcing it to happen).

Also, I don't remember if you said that it only happens when a user connects or not? The fact that no other commands were passed to Mystic on a regular telnet connection would also leave me completely confused, since usually things like '-HOST', '-IP', and '-TID' are passed on those connections.

 > So I noticed the process only very occassionaly runs ar 99% for more
 > than 2:30 minutes. I adjusted my script to only inform me when it
 > goes on longer than 5:00 minutes.

Which script is this, connect.mps? When is this specifically ran?

 > Nothing triggered the script so far. I'll probably leave it like this
 > and only reset on the rare occurrence when it runs for too long.

I wouldn't want my CPU spiked for even that long, to be honest. Why not set it for like 10-20 seconds or something? I can't imagine anything else would or should spike the CPU for that long, unless something actually hangs or gets stuck or something is wrong with your hardware - which you don't really want to happen anyways.

Have you by chance tried setting up a default install outside of your setup to see if it happens there, too? Then you can re-introduce all of your mods/scripts one by one to see if one of them triggers either the command, or the CPU spikes.

Regards,
Nick

.... He who laughs last, thinks slowest.
--- slrn/pre1.0.4-9 (Linux)
 * Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

.