Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!brl-adm!brl-smoke!smoke!lin%carcvax.uconn.csnet@csnet-relay.arpa
From: lin%carcvax.uconn.csnet@csnet-relay.arpa
Newsgroups: net.unix-wizards
Subject: trouble with socket
Message-ID: <1650@brl-smoke.ARPA>
Date: Sun, 9-Mar-86 02:52:43 EST
Article-I.D.: brl-smok.1650
Posted: Sun Mar  9 02:52:43 1986
Date-Received: Tue, 11-Mar-86 01:14:05 EST
Sender: news@brl-smoke.ARPA
Lines: 22

we use sockets(data stream with unet and inet under 4.2) 
for processes communication. At the very beginning, it gave
us much troubles and crashed the system very often. Right now
it is better, but we still have some questions.

1. On inet domain(data stream), when a socket is closed the system can 
   still transmit data between the original sockets. I have to wait for 
   a long time if I still have to use the same port numbers for next 
   socket connection.  I got "the address already used". Is there any 
   way to solve this error? (Dynamic port assigment for each connection 
   is not suitable for me.)

2. When using socket with inet for connection, the connection side is doing 
   connection and waits for listening side to accept. Before the
   listening side answers, can the process that is still 
   doing connection be able to  receive any SIGINT interrupt 
   from the other processes? It may cause "BROKEN PIPE" error.

3. The listening process will cause "BROKEN PIPE" when this process
   is listening  and an interrupt comes in(The same problem as item 2
   for listening process).