Subj : Synology Docker Mystic Test
To   : Accession
From : opicron
Date : Thu Feb 13 2025 10:02 am

 Ac> Hey fusion!
 Ac> 
 Ac> On Wed, Feb 12 2025 03:49:10 -0600, you wrote:
 Ac> 
 Ac>  > there's a bit of nuance here. reading comprehension.. i can certainly
 Ac>  > respond to a) his first idea about dumping non ansi users and
 Ac>  > separately, b) needing workarounds being disappointing re: his script
 Ac>  > to completely kill/restart mystic to restore it to a state where it
 Ac>  > will accept connections... two separate trains of thought.
 Ac> 
 Ac> Seems the reading comprehension was on your end, chief. I was _specificall
 Ac> replying to you talking about not allowing non-ansi users (even quoted it 
 Ac> second time for you, so you would understand -- guess it didn't work), and
 Ac> supplied another option to do so that Mystic itself provides besides your
 Ac> script/workaround. I wasn't replying to his message or his problem, or the
 Ac> that you wrote that script because of said problem.
 Ac> 
 Ac> It was simply stating that Mystic already had an option to not allow ascii
 Ac> callers.
 
Your solution wasnt feasible, because using that way Mystic is already unresponsive
and doesnt drop the user. Actually we cant even connect to any node. And its not
because the nodes are busy, its because Mystic become unresponsive, completely.

Again, it might have to do with server too-- or maybe the two together. Anyway
that was the issue.

With manual drops, in whichever way works out better for me.

I think no software is 100%, our creativity and workarounds are making our
lives, and indirectly the software better. 

oP!

.... Save the wales! Nuke Greenpeace instead!

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

.