burati@ULOWELL.CSNET (Michael Burati) (11/19/85)
Continueing from an earlier message about my registry files not being available from a dumb terminal connected through an sio line... It turns out that the dumb terminal had nothing to do with the problem. After unlocking the registry files with "ulkob -f /registry/rgy_site/?*" I decided not to use the sio terminal for registry work anymore. Then, using only a DN300 to add accounts, the registries became locked several more times. After trying everything I could to lock them, I found that it was the script file that I use to add accounts to our network. I have not seen anything in the documentation that instructs you not to use edacct and edppo in shell scripts, but it never fails that one out of every two times that I use the script, the rgy_site files become locked. ------------------------------------------------------------------------ Another problem that I'm having with sio lines is when I try to use the sio1 line on a dsp80 or dsp160. If I leave the terminals on (DEC vt240s) I can log off, log back on and everything is fine. If I turn the terminal off and back on again, the dsp exits down to the "Phase II shell" and I get a ")" prompt on my terminal. Is this problem particular to DEC terminals, or is it something that has been a problem with dsp's? Michael Burati Univ. of Lowell Comp Sci Dept CSNET: burati@Ulowell
JW-Peterson@UTAH-20.ARPA (John W Peterson) (11/19/85)
> If I turn the terminal off and back on again, the dsp exits down to the > "Phase II shell" and I get a ")" prompt on my terminal. This is probably due to the terminal sending spurious serial line garbage as the power goes off. For example, if the DSP recieves a "^]" character via the serial line, the SPM interprets this as a quit fault and exits back to the boot shell. Also, the SR9 SPM actually listens to commands while running. I think you can type "h" and get a list of options... -------