Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!cgwst
From: cgwst@unix.cis.pitt.edu (Gray Watson)
Newsgroups: comp.unix.sysv386
Subject: Sys V3.2 missing tty driver feature??
Summary: CLOCAL flag is broken?
Message-ID: <81197@unix.cis.pitt.edu>
Date: 19 Jan 91 01:55:56 GMT
Reply-To: cgwst@unix.cis.pitt.edu (Gray Watson)
Organization: University of Pittsburgh
Lines: 21

This probably has been hashed before here, but I can't find it in my archives.

I am having problems getting the CLOCAL flag to work with my ESIX V3.2 Rel D.
According to the manual entries, if the CLOCAL flag is *not* set, when the
carrier detect line is dropped by the modem (the remote modem hangs up or the
line is dropped) the tty driver sends a HUP signal to the process group.  I
can't get it to work.

I bet it is the driver from AT&T that is broke.  Have *any* of the ports out
there fixed this??

Questions:
a) am I right that the V3.2 tty driver does not have this implemented?
   If I am wrong then what do I need to do to get it to work.
b) anyone fix the tty driver or have a work around.  I guess I can write
   an idle-kill program that resets the line if it determines I've gone
   bye-bye, but it is a hack.

Thanks for any help.
gray
gray@med.pitt.edu