[Coco] tsmon / login

[Christopher R. Hawks]

On Sun, 1 Feb 2015 17:21:54 -0600
Allen Huffman <alsplace at pobox.com> wrote:

> At Microware, all our OS-9 systems were set up with tsmon monitoring
> the serial port(s), or the telnet daemon would launch login if you
> connected that way. I am wanting to do the same thing on OS-9/6809
> but I am forgetting something…
> 
> In my startup, I initialize some window devices…
> 
> iniz term w1 w2
> 
> …and at the end, I want to launch tsmon monitoring those devices
> 
> ex tsmon /term /w1 /w2
> 
> The one on /term works, but /w1 and /w2 never respond to ENTER.
> (Hmmm, maybe I need to echo something there to get stdin reading from
> them?)
> 
> Also, I go from 392K FREE booting to the shell, to 360K booting that
> way. In procs, I see SysGo is still running, as well as the shell it
> spawned. I thought doing the “ex” would kill off the shell that was
> processing the startup file. I think SysGo spawns a shell to process
> startup, then at the end it spawns a new shell for the user — so that
> may explain why SysGo is still there. The thing it spawned (shell
> processing startup) never exited (it became tsmon), so it’s still
> waiting.
> 
> I tried running tsmon in the background too:
> 
> ex tsmon /term /w1 /w2 &
> 
> What am I forgetting?
> 
> 		— A

	From what I see in /nitros9/level1/cmds/tsmon.asm it only
monitors one device. (Use the source Luke!)

	You'll need to run it separately against each window...

ex tsmon /term &
ex tsmon /w1 &
ex tsmon /w2 &


Christopher R. Hawks
HAWKSoft
-- 
"but alas for those who don't know that the wolves who seem sweetest are
the most dangerous of all wolves."