Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!srhqla!denwa!jimmy From: jimmy@denwa.info.com (Jim Gottlieb) Newsgroups: comp.unix.sysv386 Subject: Re: ESIX: cu does not detect dropped line. Message-ID: <705@denwa.uucp> Date: 28 Nov 90 20:17:27 GMT References: <1990Nov23.044733.1628@druid.uucp> Sender: jimmy@denwa.uucp Reply-To: jimmy@denwa.info.com (Jim Gottlieb) Organization: Info Connections, West Los Angeles Lines: 22 Summary: Expires: Sender: Followup-To: In article <1990Nov23.044733.1628@druid.uucp> darcy@druid.uucp (D'Arcy J.M. Cain) writes: >In article Kayvan Sylvan writes: >>The problem: When I use cu to dial into another system, when I log out >>and the line is dropped, cu sits there still waiting for input. It's >>almost as if the modem control does not work. I have to do "~." to get >>back to the shell. > >Check your devices. The minor number should 128 higher for lines with >modem control. Here is part of my /dev directory: I have the same problem, but I am using the Megaport 24-port card. I set up the port for modem control, and modem control does in fact work on incoming calls as evidenced by the fact that hanging up from the remote end logs out the caller. But on outgoing calls, I must always do a ~. to get out. It's not a modem configuration problem, as unplugging the cable to the modem (thereby definitely dropping CD and DSR) still doesn't end the cu(1) session. Maybe I will try the new 2.0 drivers from Equinox and see if they resolve it.