Mornin Ben,
> > Ah, good point. If the host server is aware of this service and it has
> > been virtualised (it has been configured properly in [x]inetd to run
> > through virtuald), then yes this may cause problems. Having just tried
> > it with apache, you get errors as the vs configured to bind to all IPs
> > fails to come up if there is another vs already running http, as it
> > can't bind to that address, so you're more likely to screw up your own
> > services that those on the other vs's. If the host server doesn't know
> > of the service (or it hasn't been virtualised) then there is no way to
> > get requests to the virtual server.
>
> In relation to your last sentence, in what way does the host server
> 'know' of the MySQL servers (mysqld)? 'mysqld' is run from
> "/etc/rc.vsd" on the VSs and is not 'virtualised' into /etc/inetd.conf
> on the host server? Yet MySQL requests get to the VS, don't they?
mysqld is bound to the VS's IP, and listens on a port above 1024 (3306 I
believe) so doesnt need root privs to bind to that port.
If you can imagine the IP alias is actually _bound_ to the VS under chroot,
so has a real IP assigned to it.
This comes into the area that I understand but yet still confuses me at the
same time, you need to imagine the VS as a host unto itself, and treat it
like one.
So to answer your question, MySQL requests do go straight to your VS via that
VS's IP (alias) adress.
Hope that makes sence.... =>
Cheers,
Nige
------------------------- The freeVSD Support List --------------------------
Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
Archives: http://freevsd.org/support/mail-archives/freevsd-support
-----------------------------------------------------------------------------
