TOPS-10 boots, OPSER starts CDRSTK and that goes into an infinite loop.

[Ric Werme]

This post is a bit premature, I should look into things a bit more, but it ties into my post about the console display when the system is idle.

On OPSER:

!:what all
M2      4       1,2                     ^C      00:00:00
M1      3       1,2                     ^C      00:00:00
C       5       1,2             CDRSTK  RN      00:01:01
B       6       1,2             BATCON  HB      00:00:00
L       7       1,2             LPTSPL  HB      00:00:00
PT      8       1,2             PTPSPL  HB      00:00:00
CP      9       1,2             CDPSPL  HB      00:00:00
7       10      1,2                     ^C      00:00:00
!:kill c

CDRSTK seems to be a program responsible for reading batch jobs off the card reader and queues them for execution.  Okay, it would be nice if that reads a Linux pipe or file or something, it could be a way to load files on to TOPS-10.  I can write stuff to LPT: and find it in test.log.

At any rate, it goes into a loop and the console looks way too busy. The ":kill c" kills job "c", or 5, which is cdrstk and the system goes idle and the console lights are at PC 1 in the null job, as I expected.  But they changed the null job on me, it's no longer a one instruction AOJA loop!

So, far TOPS-10 is running happily without CDRSTK, not a surprise.