levy@ttrdc.UUCP (Daniel R. Levy) (08/30/85)
Dear Net.Decus: Is there a way I can squelch the continual respawning of LOGINOUT at a VMS terminal line which would otherwise be excited by characters coming at it when it is not allocated or otherwise in use? I have a terminal line which I want to connect to Datakit as an outgoing port, to be used only as initiated from inside the VAX, not from the Datakit line. But I want then to use it for two-way communication (not like a spooled printer or the like). I have tried things like $ set terminal /nointeractive device: which does not seem to work. The problem with having LOGINOUT at the terminal is that it keeps having a constant conversation with Datakit, with a lot of Username: Password: User authorization failure while Datakit is going Username: IS AN INVALID DESTINATION Password: IS AN INVALID DESTINATION User authorization failure IS AN INVALID DESTINATION with the result that VMS and Datakit are driving each other wild. This leads to difficulties when the terminal is to be allocated, from a batch job. (I solve it by sitting in a loop trying to allocate the sucker until I catch it at just the right time or have tried a couple of hundred times with no luck). Any clues or help would be mucho appreciated. Thanks much. -- ------------------------------- Disclaimer: The views contained herein are | dan levy | yvel nad | my own and are not at all those of my em- | an engihacker @ | ployer, my pets, my plants, my boss, or the | at&t computer systems division | s.a. of any computer upon which I may hack. | skokie, illinois | -------------------------------- Path: ..!ihnp4!ttrdc!levy or: ..!ihnp4!iheds!ttbcad!levy
stew@harvard.ARPA (Stew Rubenstein) (09/01/85)
In article <389@ttrdc.UUCP> levy@ttrdc.UUCP (Daniel R. Levy) writes: >Dear Net.Decus: > >Is there a way I can squelch the continual respawning of LOGINOUT at a VMS >terminal line which would otherwise be excited by characters coming at it >when it is not allocated or otherwise in use? Yes, this is easy. SET TERM TXA1:/NOTYPEAHEAD/PERMANENT will do the trick. On VMS V4 you can set it /SYSPASSWORD and it will not only solve the login war but will still let you log in if you type the system password first. Stew
tli@oberon.UUCP (Tony Li) (09/02/85)
The trick is to $ SET TERM/PERM/NOTYPEAHEAD...
;-)
--
Tony Li ;-) Usc Computer Science
Uucp: ...!{{decvax,ucbvax}!sdcsvax,hplabs,allegra,trwrb}!sdcrdcf!uscvax!tli
Bitnet: tli@uscvaxq, tli@jaxom, tli@ramoth
Csnet: tli@usc-cse.csnet
Arpa: tli@usc-ecl.arpanrh@lzwi.UUCP (N.R.HASLOCK) (09/03/85)
In article <389@ttrdc.UUCP>, levy@ttrdc.UUCP (Daniel R. Levy) writes: > > Is there a way I can squelch the continual respawning of LOGINOUT at a VMS > terminal line which would otherwise be excited by characters coming at it > when it is not allocated or otherwise in use? This was discussed recently in fa.info-vax. The only known to work answer is Set TERM /perm/NOtypeahead. Basically this keeps the driver's buffer empty so the loginout's ast is never triggered. Allocate the line and reset the characteristic when you want to use the line. -- -- {ihnp4|vax135|allegra}!lznv!nrh Nigel The Mad Englishman or The Madly Maundering Mumbler in the Wildernesses Everything you have read here is a figment of your imagination. Noone else in the universe currently subscribes to these opinions. "Its the rope, you know. You can't get it, you know."
levy@ttrdc.UUCP (Daniel R. Levy) (09/04/85)
Thanks to everyone who wrote or posted suggesting a solution to this one. The answer I arrived at (which oddly enough nobody mentioned) was to $ SET TERMINAL /NOMODEM /PERMANENT DEVICE: and reverse that after allocating the device in the batch job. I have not yet tried the other techniques, which may work just as well. Thank you all just the same. -- ------------------------------- Disclaimer: The views contained herein are | dan levy | yvel nad | my own and are not at all those of my em- | an engihacker @ | ployer, my pets, my plants, my boss, or the | at&t computer systems division | s.a. of any computer upon which I may hack. | skokie, illinois | -------------------------------- Path: ..!ihnp4!ttrdc!levy or: ..!ihnp4!iheds!ttbcad!levy