Looking at the logs with mis2 running telnet I see:

server_telnet.log <==

Sep 01 02:35:58 0 BLOCKED 23.233.5.228 (23-233-5-228.cpe.pppoe.ca)
Sep 01 02:35:59 0 BLOCKED 23.233.5.228 (23-233-5-228.cpe.pppoe.ca)
Sep 01 02:36:01 0 BLOCKED 23.233.5.228 (23-233-5-228.cpe.pppoe.ca)
Sep 01 02:36:02 0 BLOCKED 23.233.5.228 (23-233-5-228.cpe.pppoe.ca)
Sep 01 02:36:04 0 BLOCKED 23.233.5.228 (23-233-5-228.cpe.pppoe.ca)
Sep 01 02:36:05 0 BLOCKED 23.233.5.228 (23-233-5-228.cpe.pppoe.ca)
Sep 01 02:36:07 0 BLOCKED 23.233.5.228 (23-233-5-228.cpe.pppoe.ca)
Sep 01 02:58:51 0 Connect: 24.34.40.65 (c-24-34-40-65.hsd1.nh.comcast.net)
Sep 01 02:58:52 0 Connect: 24.34.40.65 (c-24-34-40-65.hsd1.nh.comcast.net)
Sep 01 02:58:56 Shutting down

But it's Sep 2 and I'm here so I think it's running. Just checked with name
and yes it's running. Something has caused the log to stop and it didn't
start again. Since telnet is really running it's minor ;)

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

Looking at the logs with mis2 running telnet I see:

server_telnet.log <==

That is not a MIS2 log. Thats from MIS. :)

MIS2 does not have a separate log for each server type if my memory serves me.

This is because each server type can have many instances of that server type.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 09/02/17, g00r00 said the following...

Looking at the logs with mis2 running telnet I see:

server_telnet.log <==

That is not a MIS2 log. Thats from MIS. :)

MIS2 does not have a separate log for each server type if my memory
serves me.

This is because each server type can have many instances of that server type.

OK, so that makes sense. I switched off mis and started mis2 on telnet so
that was me switching it off ;)

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)