The mystic process is back slowing my system to a crawl. I never had this problem with previous versions. I can't kill the process with the kill command. I guess I'll try downgrading back to A34 and see if it goes away.


top - 11:56:43 up 2 days, 16:09, 1 user, load average: 1.09, 1.22, 1.28 Tasks: 116 total, 2 running, 113 sleeping, 0 stopped, 1 zombie
%Cpu(s): 23.0 us, 72.4 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 4.6
st
KiB Mem : 500048 total, 26792 free, 97312 used, 375944 buff/cache
KiB Swap: 0 total, 0 free, 0 used. 364300 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8104 bbs 20 0 98232 3392 2224 R 93.4 0.7 1632:12 mystic
3 root 20 0 0 0 0 S 0.3 0.0 2:03.18 ksoftirqd/0
595 bbs 20 0 40492 3604 3036 R 0.3 0.7 0:00.04 top
1647 bbs 20 0 13140 3084 2644 S 0.3 0.6 11:30.23
mrc_client.+
1654 bbs 20 0 13140 3188 2716 S 0.3 0.6 20:46.28
mis-server.+

Immortal

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 09/17/17, Immortal said the following...

The mystic process is back slowing my system to a crawl. I never had
this problem with previous versions. I can't kill the process with the kill command. I guess I'll try downgrading back to A34 and see if it
goes away.

Immortal

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

Basic kill won't work, but sudo kill -9 will - I've seen that too.
You don't need to reboot, just sudo kill -9 pid(s) then restart the processes you need (sudo ./mis -d). This works, I've been using it when those problems show up (due to hacker attacks).

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Workpoint (21:1/145.3)