This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Ports 25 and 110
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Rick Davis <rickdavisjr at comcast dot net>
- Cc: 'Ecos-Discuss' <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 4 Oct 2004 17:17:42 +0200
- Subject: Re: [ECOS] Ports 25 and 110
- References: <20041004145822.GM7625@lunn.ch> <E1CEUPs-0008I1-00@londo.lunn.ch>
On Mon, Oct 04, 2004 at 11:06:38AM -0400, Rick Davis wrote:
> Andrew,
>
> Another thing I have seen. I have a thread that listens on a port,
> 11111. When I stop the thread, I close the port. The port scanner still
> indicates it responds even after the thread has shutdown the port and
> exited. I even waited 10 minutes before scanning.
Thats probably normal. TCP sockets are kept around for a while after
being closed so that any delayed retries etc are thrown away and not
passed to a new socket which is using the same port number. If you
leave it long enough it should go away, but i don't remember what the
timeout is.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss