Return to BSD News archive
Xref: sserve comp.sys.next.programmer:10479 comp.dcom.modems:34763 comp.unix.bsd:12245 comp.unix.programmer:10441
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!cs.utexas.edu!asuvax!ncar!noao!CS.Arizona.EDU!not-for-mail
From: kline@CS.Arizona.EDU (Nick Kline)
Newsgroups: comp.sys.next.programmer,comp.dcom.modems,comp.unix.bsd,comp.unix.programmer
Subject: exit pgm w/o hanging up phone
Followup-To: comp.sys.next.programmer
Date: 12 Jul 1993 00:31:45 -0700
Organization: University of Arizona CS Department, Tucson AZ
Lines: 33
Message-ID: <21r411$2dj@cheltenham.cs.arizona.edu>
NNTP-Posting-Host: cheltenham.cs.arizona.edu
I am wondering how my program can keep from hanging up the modem after
it exits.
I have a NeXT 040 cube running os release 3.0. I have a zyxel modem.
For those in other newsgroups, this runs a bsd 4.3 / mach 2.x combo.
If there is a way to do this in bsd, then it should work here.
Looking at the man pages and the ioctl header file (joy joy),
I have found 3 suggestive calls:
#define TIOCHPCL _IO('t',2) /* hang up on last close */
#define TIOCEXCL _IO('t',13) /* set exclusive use of tty */
#define TIOCNXCL _IO('t',14) /* reset exclusive use of tty */
So, there doesn't seem to be an opposing call to TIOCHPCL which would
not hangup on last close.
If I leave all 3 of these out of the open, then it hanges up when I close.
If I put the exclusive use of tty in there it still hangs up.
I think I have used as least one program on the next which didn't hang
up after it died.
Mail me or post and I will summerize.
thanks,
nick kline
kline@cs.arizona.edu