Launch vaddhost
Connect to your Virtual Server using
Telnet or SSH
and run the vaddhost command by typing:
% vaddhost
Step 1: Virtual Host Name(s)
Virtual Host Names identify which domain names will be associated with
the Virtual Subhost definition that vaddhost will add to your httpd.conf
file. You may specify one or more domain names with each Virtual Subhost
definition. Typically, a Virtual Subhosted domain name will at the very
least include the "www.domain.name" and "domain.name" Virtual Host Names.
Step 2: Virtual Host Admin E-mail Address
The Host Admin E-mail Address identifies the e-mail address of the person
responsible for the web site of the subhosted account. If the e-mail
address you specify will be a E-mail account on the Virtual Server, you
will need to use the vadduser
program to add the e-mail account separately.
Step 3: Virtual Host Document Root
The Virtual Host Document Root is the directory where the web site
content for the Virtual Subhost will be stored. The value of the Document
Root is defined with respect to your home directory, so you need not
preface your definition with "/usr/home/[your login id]". The default
value for the Document Root directory is located in your "vhosts"
directory. This is to insure compatibility with the latest version of
Microsoft FrontPage should
you decide to install Microsoft FrontPage at a later date.
Step 4: Transfer and Error Log Files
You can (if you choose) specify separate transfer and error log files for
each Virtual Host. This is an optional feature. If you do not wish to
store separate logfiles for the Virtual Subhost, the transfer and error
log information will be stored in the web server's master log files.
If you do wish to store separate tranfer and error log files, vaddhost
will provide you with several options based on the input you provided
for the Virtual Subhost Document Root.
Step 5: cgi-bin Directory
You can also (if you choose) configure a cgi-bin directory for your
Virtual Host. This is an optional feature. The cgi-bin "ScriptAlias"
directive defines where CGI scripts are stored for the Virtual Subhost.
It is important to understand that giving cgi-bin access to your
Virtual Subhosted clients is a potential security risk. This is
because the CGIs your customers upload and execute have all of the
rights and privileges of the CGIs you execute. See our document,
Virtual Subhosting security issues for
more information.
