Subj : Re: Synology Docker Mystic Test
To   : opicron
From : fusion
Date : Fri Feb 07 2025 08:56 pm

On 07 Feb 2025, opicron said the following...
 
 op> When I was running Mystic a46 there werent any issues. This all
 op> occured when moving to a48/a49. It must be my server configuration
 op> together with that version, as nothing else changed.

why not run a46? is there something significant you can't live without?

 op> Thanks for your insight ^^, wouldnt you take this solution seeing the
 op> time and benefits?

no.

http://kirin.dcclost.com/~alex/opicron.c

i tested this a bit but i can't do everything first try ;) maybe a second set of eyes will help. it decouples server connections from mystic node connections.. so even if 1000 people connect at the same time only the one that hits 'ESCAPE' will spawn an actual mystic process/use a node..

change line 138 to the directory mystic is in and build with

gcc opicron.c -o opicron

in MIS you'll have to swap the telnet server to a different port, or disable
it entirely. obv MIS would still run for binkp, events, SSH, etc..

if that works for a while and instead hammering SSH is what causes it, well, maybe libssh can be made to do the same thing this does..

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

.