PEEK gets stuck in a loop typing out tty line information sometimes

[dseagrav]

When peek is asked to type out tty line information for a job that might not have one, it gets stuck in a loop. This happens with things that don't have a tty (COMSAT et al.) and sometimes when jobs are started from TCP connections that don't properly close. When this happens, the tty is described as being in COM mode with an endless list of terminals. Example output follows, I typed P^K to summon peek and then 3L to type the line information for job 3, COMSAT.
Unrelated output of peek was replaced with (etc etc) for brevity.

P^K(Please Log In)
!

SE ITS 1652  Peek 632   1/9/2025 (etc etc)
  3 COMSAT JOB.07 SYS        HANG    ?         3   0   0%          6
(etc etc)
Fair Share 80%     Totals:                   285      12%      25:38
Logout time = 47:51   Lost 0%  Idle 57%  Null time = 22:04:21


3L
SE ITS 1652  Peek 632   1/9/2025 07:54:18  Up time = 1:02:24:41
TTY Ix Uname  Jname    Type        V-size  H-size Com   Bits    Idle-min
35   3 COMSAT JOB.07                132       1   C                  -
 in COM link with T100, T 5, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SY!
S, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS, T 0, SYS!

This will repeat forever until interrupted by the pager or the user typing something that interrupts it.

This behavior has been observed on a physical KS10 and in the KA emulator.