Q:Socket bind

Q:Socket bind

Post by Maast » Sat, 09 Sep 1995 04:00:00

Running on Sol 2.4. Why does the socket hang around after both the server
and clients have been killed off? It takes about 3 min before you can
restart the server, that is assuming that you keep using the same port. Is
there some way to get around this?




1. using bind() to bind socket to device

  I'm interested in binding a socket to a device, and have looked at
the pcap source code. In pcap-linux.c, a generic socket address
stucture is used, and a string containing the name of the device to
use is placed in the data portion.  This address structure is then
used in the call to bind.  This seems odd to me and I haven't figured
out from the sock man page why this would work.  The packet man page
suggests using a sockaddr_ll structure, which contains the hardware
address of the device, in the call to bind.  Any idea why this first
method which seems bizzarre to me, would work?

2. MultiBoot LILO question

3. Bind: socket operation on non-socket

4. Linux SAMBA server viewed as being on the Internet by XP

5. help: close(socket) leaves socket bound ?

6. libgdb

7. Sockets: server close leaves socket bound?

8. Netfinity 5100 and 4 Eepro100 Nics

9. bind: socket operation on non-socket

10. sockets v/s Message Qs

11. Binding a DGRAM (UDP) socket?

12. binding socket

13. Berkeley Socket 'bind' system call