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

 Ac> From the questions I wrote above, I'm just wondering if possibly when an e
 Ac> is triggered maybe this command is ran by MIS itself to check if a user is
 Ac> online, and compare it to whatever configuration settings are set.

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.

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.

 Ac> In mystic -cfg > Configuration > General Settings:
 Ac> 
 Ac> What do you have set for "Disable Time"? If no, try setting it to yes for 
 Ac> couple of days and see if you see that command triggered again during that

I tried to disable time and have timeout set to 0 for a few days. No change
unfortunately.

 Ac> In mystic -cfg > Editors > Event Editor:
 
 Ac> Do you have anything besides "0" under "Warning" (last option) in any of y
 Ac> events? If so, try setting them back to "0".

All events are set to 0.

 Ac> That's about all I can see that could possibly trigger something like that
 Ac> events come into play, or even when users are online, as far as configurat
 Ac> settings would go.

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.

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.

oP!

.... A:  I don't know  and I don't care.

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

.