Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!snorkelwacker!mit-eddie!uw-beaver!zephyr.ens.tek.com!tektronix!upvax!stevewa
From: stevewa@upvax.UUCP (Steve Ward)
Newsgroups: comp.unix.questions
Subject: Re: Sys V uugetty problem
Keywords: sys V, uugetty, cu
Message-ID: <1061@upvax.UUCP>
Date: 17 Feb 90 06:55:53 GMT
References: <20286@bcsaic.UUCP> <97213@linus.UUCP>
Reply-To: stevewa@upvax.UUCP (Steve Ward)
Organization: University of Portland, Portland, OR
Lines: 27

In article <97213@linus.UUCP> rtidd@mwunix.mitre.org writes:
>In article <20286@bcsaic.UUCP> carroll@bcsaic.UUCP (Jeff Carroll) writes:

>>	uugetty handles incoming calls OK, but when I try to use cu to
>>dial out, it doesn't seem to be able to open the tty line. Running   
>>cu -d -ltty00 the system tells me "CAN'T ACCESS DEVICE".

>I wish I could help you, but I can only agree with you. I normally use
>kermit to dial out, and when I have uugetty running on my serial port
>kermit will run fine, but when I tell it to connect to the tty it
>just hangs... no error message or anything, it just freezes.

The problem seems to be with kermit.  I think it's not putting the lock file
where uugetty expects to see it, or something.  I have to manually turn off
the uugetty to use kermit, but cu _usually_ works OK.  Sometimes even turning
off uugetty isn't enough, and I have to reboot with the uugetty turned off in
order to make everyone happy.

If someone has solved this problem for real, PLEASE PLEASE PLEASE post your
solution!!!!!!

Steve
-- 
| Steve Ward Jr. appears courtesy of       |            stevewa@upvax.UUCP    |
| Univ. of Portland, Portland, OR          |         !tektronix!upvax!stevewa |
| (insert disclaimer here)                 |  upvax!stevewa@tektronix.TEK.COM |
| --If all else fails, try:      tektronix.TEK.COM!upvax!stevewa@uunet.uu.net |