Re: post-2.3.12 pending stuff in my private work area

Steve G <[email protected]> writes:

>>2. a new "libwrap" option to let me configure the name 
>>that libwrap is given for looking up if access is to be
>>allowed.
>
> You shouldn't need this. tcpd always uses the basename of
> the full path to the server.

That's the problem. Who says I can't use the same server executable with
different environment variables and different access control lists on
different ports? If I'm going to do that, I'll have to write shell
wrappers. The libwrap feature trivially eliminates the need for the
additional shell start.

> Think of inetd, there is no where to pass the name of what
> you want tcpd to think the name is. Its implicit in the
> command line.

xinetd is not inetd.

-- 
Matthias Andree