The interworking between TCP-wrapper and xinetd is not very clearly described
in BLFS (I use Version svn-20110417).
- The TCP-wrapper page mentions: "Similar changes must be made if xinetd is
used, with the emphasis being on calling /usr/sbin/tcpd instead of calling the
service daemon directly, and passing the name of the service daemon to tcpd.",
which is not at all clear to me.
- the xinetd page only mentions TCP-wrapper as an optional dependency.
What I had to do to integrate both applications:
1. add --with-libwrap to the configure command for xinetd;
2. replace in the configuration files for xinetd the line
"server=/usr/sbin/in.<myserver> by:
flags = NAMEINARGS
server = /usr/sbin/tcpd
server_args = /usr/sbin/<myserver>
I now find in /var/log/daemon.log:
(…)
May 8 20:35:18 ppc7600 xinetd[312]: Reading included configuration file:
/etc/xinetd.d/ftp [file=/etc/xinetd.d/ftp] [line=12]
May 8 20:35:18 ppc7600 xinetd[312]: Reading included configuration file:
/etc/xinetd.d/telnet [file=/etc/xinetd.d/telnet] [line=12]
(…)
May 8 20:35:19 ppc7600 xinetd[312]: xinetd Version 2.3.14 started with libwrap
loadavg options compiled in.
May 8 20:35:19 ppc7600 xinetd[312]: Started working: 2 available services
So, I think this is the correct procedure.
pvg
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
