Xref: utzoo comp.unix.questions:10863 comp.unix.wizards:13790
Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!csd4.milw.wisc.edu!nic.MR.NET!umn-cs!bungia!zeno!gene
From: gene@zeno.MN.ORG (Gene H. Olson)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: uugetty on Altos not behaving properly?
Keywords: uugetty cu uucp
Message-ID: <323@zeno.MN.ORG>
Date: 31 Dec 88 20:27:05 GMT
References: <344@cpmain.UUCP>
Reply-To: gene@zeno.UUCP (Gene H. Olson)
Organization: Smartware Consulting, Minneapolis, MN
Lines: 32

Chances are your problems stem from one of the two problems below:

1)	The ALTOS cu does not create a lockfile.  It has been that
	way for at least 5 years, and although the problem has often
	been reported, ALTOS does not seem to think it is an important
	problem to solve.

2)	Modem control doesn't work.   Uugetty requires that cu can open
	the tty port with NDELAY, change the mode to CLOCAL, then turn
	off NDELAY and proceed to dial out and communicate.   This screws
	up really bad on the ALTOS, and differently depending on the
	revision of the operating system, and the type of serial port
	you are using.

As you might guess, I am quite bitter about the above.  I have
suffered with kludges to avoid both of these for years.  My
advice is to:

1)	Replace cu (if you can) with a shell script that sets the
	lockfile,  and

2)	Force CD on the modem so the ALTOS never sees CD drop which
	is what upsets it.

This is really cludgy,  however experience says it *will* work
*most* of the time.


Gene H. Olson
Smartware Consulting
Minneapolis, MN
gene@zeno.mn.org