[net.eunice] Disabling logins on a port?

lwall@sdcrdcf.UUCP (Larry Wall) (10/15/84)

*** MASSAGE THIS LINE WITH YOUR REPLACE ***

I've got two Eunice sites that I'm trying to get to talk via uucp.  One
problem I've been having is that occasionally the line starts "ping-ponging".
Site A sees garbage on the line and says "Username: ", and eventually times
out.  But then Site B see the stuff sent out by Site A, and says "Username: ",
etc, etc.  Not only does this fill up our accounting file, but it prevents
uucp from running, tragedy of tragedies.

We only poll in one direction, say from Site A, so I ought to be able to
suppress login processing on the A side, which would solve the problem.
The only way I've found so far, however, involves allocating the terminal
line in question.  The problem with this is that the line has to be
allocated by the uucp process, which isn't there all the time, so I can't
allocate it permanently.

I've glared at the manuals for a considerable length of time, and have yet
to see any simple way of telling VMS not to respond to garbage on the line.
On my Unix system, I just edit /etc/ttys and zap init.  Is there anything
comparable under the Virtually Mindless Sadist?  Help, Cecil, help!

Larry Wall
{allegra,burdvax,cbosgd,hplabs,ihnp4,sdcsvax}!sdcrdcf!lwall

tihor@acf4.UUCP (10/17/84)

Just disable typeahead on the terminal in question.  The moral equivalent of
getty/init waiting on a terminal line is the JOB_CONTROL process sic-ing a
unexpected input AST on the terminal line, which requires typeahead be enabled.

jss@sjuvax.UUCP (Jonathan Shapiro) (10/31/84)

[Aren't you hungry...?]

	You can't disable logins on a port under VMS.  We had a similar
problem using Novation smartcats, and eventually replaced those with
smartmodems.  In any case, the gist of the problem is that you

	a) don't have /HANGUP set on the modem line on the VAX w/ VMS

	b) don't have both carrier detect and DTR wired.  If these are
		wired correctly the VAX will hang up after a bad login,
		which eliminates the ping pong condition.  It may take a
		few trys, but it sounds like the problem is the modem cable.

Jonathan S. Shapiro

tihor@acf4.UUCP (11/05/84)

		You can't disable logins on a port under VMS.  We had a similar
	problem using Novation smartcats, and eventually replaced those with
	smartmodems.  

Gosh.  If I disable TYPEAHEAD on a port it no one will get a login prompt 
from it, and all that.  It even says so in the manuals.

kvc@scgvaxd.UUCP (Kevin Carosso) (11/06/84)

John Shapiro writes:

>	You can't disable logins on a port under VMS.

You can disable login ports under VMS.  If you have an application that
uses the port all the time, the simplest thing to do is just ALLOCATE
the line.  If you don't have something out there all the time, but want
to disable logins, you simply set the line /NOTYPEAHEAD.  This prevents the
job controller from ever seeing unsolicited data and starting up a
LOGINOUT.  Our UUCP just sets the line /TYPEAHEAD when it starts up.
That way, when it's done and exits, the line is deallocated and automatically
reverts to /NOTYPEAHEAD.

	/Kevin Carosso       {allegra, seismo, ihnp4}!scgvaxd!engvax!kvc
	 Hughes Aircraft Co.