Re: Killing Sockets
Date: 28 Mar 2005 22:21:58 -0800
Hi,
You could try setting REUSEADDR on the socket within your application.
That should allow a second instance of the server to bind to the port
even while the old one is still hanging around.
GSF
Relevant Pages
- Re: Java Error
... number corresponds to a particular "server" application but it doesn't have ... Normally TELNET can be found when you connect to port 23 from ... The bind() call references the structure mentioned above. ... specify that port and IP address in the destination fields of the IP header ...
(bit.listserv.ibm-main) - Re: Good security related article
... A HTTP server has to bind to port 80, ... a process can give up root privileges ...
(borland.public.delphi.thirdpartytools.general) - Re: FreeBSD 7.1 and BIND exploit
... If you have a server that is running ... BIND, update BIND now. ... Make sure that you are not specifying a port via ... queries behind a one-to-many NAT using pf, ...
(freebsd-stable) - RE: IIS 6 does not start
... When you launch IIS 6.0 on a .NET Server machine, ... If an application is already using port 80 on any IP address and you then ... Once this has happened no additional processes can bind to port 80 on any ...
(microsoft.public.inetserver.iis) - RE: The process cannot access the file...
... When you launch IIS 6.0 on a .NET Server machine, ... If an application is already using port 80 on any IP address and you then ... Once this has happened no additional processes can bind to port 80 on any ...
(microsoft.public.inetserver.iis) |
|
