Re: Listening on many ports on Linux

From: Linards Ticmanis <ticmanis@xxxxxx>
Date: Wed, 07 Nov 2007 23:16:21 +0100

mowaiskhan@xxxxxxxxx wrote:

Hello,
I've implemented an Inetd type daemon in C++ language using Linux
native Socket APIs.It can listen on multiple ports and fork a process
which takes over connection just like Inetd.
I want to ask if i make this daemon to listen on fourty(40) thousand
ports.What are the Pros and Cons of this approach? Thanks.

What exactly are you trying to achieve? Depending on that, raw sockets
might be a valid approach.

--
Linards Ticmanis
.

References:
- Listening on many ports on Linux
  - From: mowaiskhan

Prev by Date: Re: Is there any point to full host names in /etc/hosts ?
Next by Date: Re: Is there any point to full host names in /etc/hosts ?
Previous by thread: Re: Listening on many ports on Linux
Next by thread: How to write a packet onto the net (or read from the net) with priority
Index(es):
- Date
- Thread

Relevant Pages

Re: Listening on many ports on Linux
... I've implemented an Inetd type daemon in C++ language using Linux ... native Socket APIs.It can listen on multiple ports and fork a process ...
(comp.os.linux.networking)
Listening on many ports on Linux
... I've implemented an Inetd type daemon in C++ language using Linux ... native Socket APIs.It can listen on multiple ports and fork a process ... which takes over connection just like Inetd. ...
(comp.os.linux.networking)