Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!peregrine!ccicpg!felix!tgate!ka3ovk!teemc!fmeed1!hpuinda!hpfcse!hpfcmgw!rdg
From: rdg@hpfcmgw.HP.COM (Rob Gardner)
Newsgroups: comp.sys.hp
Subject: Re: uugetty doesn't print /etc/issue (HP-UX 6.5)
Message-ID: <1080078@hpfcmgw.HP.COM>
Date: 29 Aug 89 21:32:28 GMT
References: <3628@fmeed1.UUCP>
Organization: HP Fort Collins, CO
Lines: 22


> >I don't know why uugetty doesn't print /etc/issue, but just out
> >of curiousity, what is your reason for using uugetty?
> 
> uugetty should be used when a TTY port is shared for dial-in & dial-out.
> uugetty understands about uucp lock files and will defer to a uucp dial-out.
> getty can and usually does "get in the way".

It shouldn't. That is uugetty's usual function on non-HPUX systems,
but HPUX has had shared dial-in/dial-out port support for years and
years and years. Take a look at the sys admin manual; It explains
how to set up the device files so that the getty will remain
hung throughout a uucp or cu session without interference. The
opposite is also true: uucp or cu will be shut out while a live
incoming call is in progress.

The fact that we have this capability is what prompted me to ask
why somebody would use uugetty. I thought perhaps they had some
special situation that warranted it (ie, hardwired direct connection),
or maybe they just didn't know about this capability.

raab