Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!cbnews!cbnewsm!jrh2 From: jrh2@cbnewsm.att.com (jay.r.harbeston) Newsgroups: comp.sources.d Subject: Re: unix Pcomm problems Message-ID: <1991Jan7.153821.18652@cbnewsm.att.com> Date: 7 Jan 91 15:38:21 GMT Distribution: usa Organization: AT&T Bell Laboratories Lines: 46 Keywords: Pcomm problems Summary: fix for uugetty and pcomm > In article <3044@polari.UUCP> kentkar@polari.UUCP (kent karrer) writes: > < > < > < > < 1. I have to go to great lengths to modify my inittab file and kill > < the active uugetty that I have set up on my com port. > < To get around the problem with the uugetty holding the line, you have to tell uugetty out of the way.. to do this firstcheck for a lock file on the port in /usr/spool/locks. Next, place a lock on the lock file using fcntl and the F_SETLK. Now open the port and the place a lock on the /dev/ttyxx device. Next, remove the lock on the lock file and close it. And you can now communi- cate with the fool thing! > < 2. After downloading files I am unable to communicate with the remote > < system. > < Put some debug code in to check and make sure that the ioctl modes are getting reset properly for both the incoming and outgoing ports. Something is probably not reset right. > I have pcomm working on a Sun Workstation, but it will not talk with the > modem on my ISC system either. I would appreciate suggestions as well. > -- try the above! Jay Harbeston