No. If you configure the AOLserver this way, you run all AOLservers from
a single process. The config I showed uses a single IP address and port,
using only the Host header to direct requests internally among the
different configured virtual servers in the one process.
Depending on the scale of your hosting operation, this may or may not be
what you want to do (for smaller-scale operations, or operations in which
security is more of a concern, I think nsvhr/nsunix is preferable, but for
operations where the chief concern is number of sites, the host-based
virtual hosting is preferred.
Pete.
On Wednesday, January 15, 2003, at 04:56 PM, Tim Moss wrote:
Actually one further question - do you need to have separate nsd processes
for each of these servers?
I guess what I'm asking is does this allow you to have one server
listening
on the same IP/port doing host based virtual hosting, to server different
sites?
regards,
Tim Moss
SiteSpeed Ltd
Mobile: 0 77 9613 4891
Email: [EMAIL PROTECTED]
Website: http://www.site-speed.com
This email contains information from SiteSpeed Ltd, which may be
privileged
or confidential. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this
information
is prohibited. If you have received this electronic message in error,
please
notify us immediately.
-----Original Message-----
From: Tim Moss [mailto:[EMAIL PROTECTED]]
Sent: 15 January 2003 20:44
To: AOLserver Discussion
Subject: RE: [AOLSERVER] AOLserver 4: Virtual server fix
Thanks Peter,
That all makes sense - I'll give it a go ASAP
(Currently using nsrewrite to achieve simple virtual hosting -
but there are a few issues)
regards,
Tim Moss
SiteSpeed Ltd
Mobile: 0 77 9613 4891
Email: [EMAIL PROTECTED]
Website: http://www.site-speed.com
This email contains information from SiteSpeed Ltd, which may be
privileged or confidential. If you are not the intended
recipient, be aware that any disclosure, copying, distribution or
use of the contents of this information is prohibited. If you
have received this electronic message in error, please notify us
immediately.
-----Original Message-----
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf
Of Peter M. Jansson
Sent: 15 January 2003 20:31
To: [EMAIL PROTECTED]
Subject: Re: [AOLSERVER] AOLserver 4: Virtual server fix
On Wednesday, January 15, 2003, at 03:16 PM, Tim Moss wrote:
I'd hear that AOLserver 4 had host-based virtual hosting
built into it.
How do you actually configure this?
More or less like this:
----------------------------------------------------------------Cut
here--------------------------
ns_section ns/modules
ns_param nssock ${bindir}/nssock${ext}
ns_section ns/module/nssock
ns_param port $httpport
ns_param hostname $hostname
ns_param address $address
ns_section "ns/servers"
ns_param server1 "Some server"
ns_param server2 "Some other server"
ns_section ns/module/nssock/servers
ns_param server1 www.server1.com
ns_param server2 www.server2.com
#
# Note that the previous section is different from the sample config
shipped
# with AOLserver 4; by empirical methods, I realized that the sample is
# incorrect -- it wants to put ":$httpport" after the host. It would be
nice if that worked,
# but the code doesn't actually support it. If you have a server
listening on
# more than one port, and you want servers with the same name but
different
# ports going to different servers, you're out of luck for now.
#
#
# Now, one set of server configs per virtual...
#
ns_section "ns/server/server1"
ns_param pageroot /usr/local/aolserver/servers/server1/pages
ns_section "ns/server/server1/module/nslog"
ns_param file "$logdir/access-server1.log"
ns_section "ns/server/server1/modules"
ns_param nslog ${bindir}/nslog${ext}
ns_section "ns/server/server2"
ns_param pageroot /usr/local/aolserver/servers/server1/pages
ns_section "ns/server/server2/module/nslog"
ns_param file "$logdir/access-server2.log"
ns_section "ns/server/server2/modules"
ns_param nslog ${bindir}/nslog${ext}
----------------------------------------------------------------Cut
here--------------------------
I left out some things, but most of those are no different from the 3x
config. Note that you load nssock on a global basis, not a per-module
basis. At the moment, it appears that nslog can only be loaded on a
per-module basis, so you can't dump all the access log entries into one
log file; that may or may not suit your taste, depending on how you run
your railroad.
Also, virtual server configuration appears static at the
moment; as far as
I can tell, you can't add servers to an AOLserver once it's completed
initialization, so dynamic virtual hosting scenarios are not
possible now.
(At Primehost, we used to solve this by lumping a number of
virtuals into
one AOLserver instance, and tuning the number of virtuals to keep the
server startup time fairly low; then we'd run as many instances as we
could get away with on a box. Some platforms could handle more
instances
with fewer virtuals per instance, and others were better at fewer
instances with more virtuals per instance.)
Pete.
