Path: utzoo!mnetor!uunet!mcvax!prlb2!kulcs!dannyb
From: dannyb@kulcs.uucp (Danny Backx)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Need help with UNIX tcp
Message-ID: <1155@kulcs.UUCP>
Date: 24 Feb 88 15:51:43 GMT
References: <8802181625.AA27348@cod.nosc.mil>
Reply-To: dannyb@kulcs.UUCP (Danny Backx)
Organization: Katholieke Universiteit Leuven, Dept. Computer Science
Lines: 32
Keywords: TCP options status
Summary: TCP features considered necessary

> sometimes do it on UNIX.  The problem simply stated is
> this: the user process cannot get the status of its
> tcp connections from UNIX.
[...] 
> Have any UNIX guru-types ever considered offering a
> 'status(myconnect)' call?  We'll gladly pay for one.
> Or even just a 'signal(YOURCONNECTISBOGUS,letmeknow)'
> would be nice?
[...] 
> Merle Neer
> neerma@nosc

Could you post a more complete list of what you think a user interface to TCP
should include ?

As for your request on 'YOURCONNECTISBOGUS', I think you can arrange something
like that on BSD. (I don't know whether you're talking about BSD or Sys-V).
If you are interested, look in the manual entries for socket(2),
setsocketopt(2) - look for the SO_KEEPALIVE option.
I'm not sure if you can detect dead connections with select(2), or maybe
with SIGIO or SIGURG.

If you find a way, please post it. I'm sure lots of people are interested.

	Danny

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 Danny Backx                            |  mail: Katholieke Universiteit Leuven 
 Tel: +32 16 200656 x 3537              |        Dept. Computer Science
 E-mail: dannyb@kulcs.UUCP              |        Celestijnenlaan 200 A
         ... mcvax!prlb2!kulcs!dannyb   |        B-3030 Leuven
         dannyb@kulcs.BITNET            |        Belgium