- Kermit/telnet negotiations work now: fd var was not being set, so
write() was not actually working
- with many controllers, Primos would halt with tumble table overflow:
you can't do read processing until lines are enabled
- only look for new connections when handling the clock line
controller; there is no sense doing this more than 10x per second, and
it probably should still have a timer in case polls are being sped up
- use buf[] for tty message, not another static buf
- when a new connection occurs, set devpoll for the controller. The
first connection to a controller was taking 5 seconds when more than 1
controller was present
- when status is read and an eor occurred, do read processing again
rather than waiting for the next poll
- divide tumble table space up by # of connected lines. The old way
read MAXREAD (64) chars from each line until the tumble table was
full. But with 8 AMLC boards configured, there is only 53 words of TT
space in each double buffer. A select() on connected fd's would be
better.
- allow # as first character of amlc.cfg for comment lines
- turn on TCP/IP NODELAY (disable Nagle) to improve character echo
for serial device servers connected to a serial printer for example,
where the SDS initiates the telnet connect to the Prime when the
printer is turned on.
