Virtual Hosting in Inetd
 Based on BSD4.4-Lite's Inetd - Put together by Matt (panzer@dhp.com)

12 Sep 95 - Alpha Release 1

I've been running this for about 6 weeks, but haven't been testing it
very hard. You are given the ability to attach services to a certain 
machine along with on a certain port.  Including things like ftp, web 
servers, telnet clients, etc.

Stand inetd.conf files are perfectly acceptable.  To attach a service to 
a hostname, you need to make a small change.
normal:
telnet  stream  tcp     nowait  root    /usr/sbin/tcpd  /usr/sbin/in.telnetd
virthost:
telnet^dhp.com stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.telnetd

This will attach telnet to the host "dhp.com".  If you do not trust 
resolver informatoin, use IP numbers instead.  Please note, that if you 
do this, then you be attaching to only "dhp.com", connections to the 
loopback interface will be ignored.

If you just want to change somethings you can add the standard line, then
the line for the host you want to change.  For example, say you have 20
virtual hosts attached to one machine.  You want telnetd running on all of
them, however, you want some custom pager software running on
pager.dhp.com.  You would want to do this:
telnet  stream  tcp     nowait  root    /usr/sbin/tcpd  /usr/sbin/in.telnetd
telnet^pager.dhp.com stream tcp nowait root /usr/sbin/tcpd /usr/sbin/pager

Standard telnet will answer on virtual-hosts, except on the virtual host 
"pager.dhp.com" which would get /usr/sbin/pager when connecting in.

If/When you have problems, drop me a line, and I can help out.  I only 
typed these docs out for a quick reference, and expect typos, and 
information that is probably just wrong.  And if you have any patches, or 
other changes I should make to this one night hack, please also send them in.

-Matt (panzer@dhp.com)


