From owner-freebsd-questions Thu Jun 27 20:18:02 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA01299 for questions-outgoing; Thu, 27 Jun 1996 20:18:02 -0700 (PDT) Received: from sili.adn.edu.ph (info@sili.adn.edu.ph [165.220.57.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA01202 for ; Thu, 27 Jun 1996 20:17:04 -0700 (PDT) Received: (from info@localhost) by sili.adn.edu.ph (8.6.11/8.6.9) id LAA01665; Fri, 28 Jun 1996 11:32:26 +1000 Date: Fri, 28 Jun 1996 11:32:26 +1000 (GMT+1000) From: Information Help Desk To: John McNamee cc: FreeBSD Questions Subject: Re: trouble for process to be terminated In-Reply-To: <199606280222.TAA02047@smoke.microwiz.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Jun 1996, John McNamee wrote: > I think your basic problem is using the ttyXX rather then cuaXX device. > mgetty needs to open the tty device and talk to the modem before carrier > is detected. The hung process is probably caused by mgetty doing an open() > on the tty device, and being blocked in the tty driver waiting for carrier. > My guess is that the modem on your COM1 is asserting CD all the time, but > the modem on COM2 is only asserting CD when connected. > > -- > John McNamee MicroWizards > Voice: 702-825-3535 / FAX: 702-825-3443 http://www.microwiz.com > HI !!! I was using the same modem when I when I connected it to COM1 and also with COM2. I just have to transfer the cable to connect to COM2. Also, I tried cuaa1 instead of ttyd1, but still I had the same problem. The mgetty process finds it hard to terminate. Based from the lights on the modem, I just see two light up and CD is not one of those which indicates that CD is not asserted all the time. Thank you. -- jf