Tom Fitzgerald writes:
> Anything you can do with inetd you can do with tcpwrapper - there's no law
> that tcpwrapper has to exec argv[1], it could invoke one of several daemons
> depending on the source of the incoming connection. This sounds ugly, though,
> and inetd is probably a better thing to hack.
>
> If you do create an inetd that can invoke different daemons on the same
> port depending on the peername, could you post it? This sounds *very*
> useful.
A good starting point for hacking on inetd might be the xinetd stuff
that was posted from Boulder, Colorado (don't remember the author).
In fact, it might even do what's needed, but I don't remember the
details.
g.
References:
|
|
