Finally just recovered from an mis crash where ps -ef | grep mis shows
multiple mis running. I did sudo killall mis waited a few seconds and did
sudo ./mis -d to start it up again and was able to login (the original problem). So the old looping is still needed for mis to recover from these random crashes.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 09/08/17, bcw142 said the following...

Finally just recovered from an mis crash where ps -ef | grep mis shows multiple mis running. I did sudo killall mis waited a few seconds and did sudo ./mis -d to start it up again and was able to login (the original problem). So the old looping is still needed for mis to recover from
these random crashes.

I'm still seeing this behavior on the Pi as well. Last night, MIS2 with ssh
was working fine, but MIS, running telnet, was crashing. So I changed up MIS
to only run an FTP server and moved both telnet and ssh to MIS2.

Well today, MIS stayed up and MIS2 dropped out. Makes me wonder if the telnet server isn't the issue somehow.

I'm not going to roll back the binaries just yet though. I'd like to see what happens.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

On 09/08/17, Zero Reader said the following...

I'm still seeing this behavior on the Pi as well. Last night, MIS2 with ssh was working fine, but MIS, running telnet, was crashing. So I
changed up MIS to only run an FTP server and moved both telnet and ssh
to MIS2.

I killed all the mis clones (sudo kill -9 PIDs). Then switched mis2 telnet
on, left binkp on mis, restarted mis -d and it's been running since with no
mis clones. I suspect this will work on most Pi setups with the 9/7 A35
version (The one Paul hatched out). I tried ftp after and it worked, so the other servers should work. Try that setup, it's working for me.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

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

I killed all the mis clones (sudo kill -9 PIDs). Then switched mis2
telnet on, left binkp on mis, restarted mis -d and it's been running
since with no mis clones. I suspect this will work on most Pi setups
with the 9/7 A35 version (The one Paul hatched out). I tried ftp after
and it worked, so the other servers should work. Try that setup, it's

This is basically what I was doing when MIS2 was failing. But I'll try
putting Bink back on MIS as you suggested and see if that sorts it out.

Honestly, I don't mind using the older version for the stability of it until things get worked out.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)