`TSMon /term&` crashes the system

[Nitrobotics]

Just to see what would happen, "I messed around and found out"...
and I messed around and found out, "just to see what would happen"...

tsmon /term&

[boisy]

Thanks for posting this issue. This was on the F256 platform. I wonder if it would also crash on a CoCo 3.

[Deek]

Does ex tsmon /term work? I ask because the boot I use doesn't run shell on /term, it runs Bill Nobel's mtsmon (which has a config file containing a list of device names to put logins on). I have login running on /term, /w1, /w2, and /w3.

[Nitrobotics]

ex tsmon /term and ex tsmon /term& both work, but from the new Shell if you kill the Tsmon process, things go haywire the same way as if tsmon /term& is run.

[Deek]

ex tsmon /term and ex tsmon /term& both work, but from the new Shell if you kill the Tsmon process, things go haywire the same way as if tsmon /term& is run.

Well, 'ex' exits the current shell as part of running tsmon, so exiting that would leave nothing running on /term, as if you had exited the default shell. What happens if you do that on f256? It leaves an idle window on a CoCo 3.

[Nitrobotics]

The issue reported is TSMon /term& and it should probably be tried on all ports to find out more.

[Deek]

The fundamental thing I am 'concerned' about is that tsmon doesn't actually do anything to crash the system.

I'm not even seeing it doing anything unusual, unless you count the thing you explicitly did wrong "on purpose" with tsmon /term& -- that is, running a program that is trying to control the terminal while leaving another program that's already controlling the terminal still running.

If I don't try to leave both shell and tsmon running concurrently on the same terminal, I can't get anything weird to happen. Even if I do leave both running, nothing seems to actually be crashing (I wind up with input going to either shell or tsmon, which is basically what I would expect).

At least on CoCo, I don't see a bug here.