Ah, OK, so I got that backwards...? So it's Tops-10 reporting a
malformed request from NML by crashing, then.? Alright, it's a misfeature.
Did you happen to have a crash dump?? I might like to take a look after
I get Kermit-20 behaving better (and after I figure out what's what with
K10MIT, sigh)
100 students?? That's all?? Heh...? I can't even remember how many we
had online with six 20's, but it didn't matter.? If one of them went
out, you got your choice of machine room phone color: bright red hot or
white hot. ? Been there, done that.? Glad I'm not doing it any more.
------------------------------------------------------------------------
On 11/10/21 4:22 PM, Robert Armstrong wrote:
It is certainly true that NML might be choking on
legitimately bogus
monitor data.
? Actually, we?re talking about the other way around ? the monitor is
choking on, maybe legitimate maybe bogus (nobody knows at this point),
data from NML.
However, one hesitates to observe that signaling
incorrect input by
crashing is a misfeature...
? No, one doesn?t hesitate in my universe?? Especially when we?re
talking about crashing a timesharing operating system with maybe 100
users logged in, most of whom are students frantically trying to get
their homework finished before class starts in ten minutes :)
Bob