OK the 'localhost' word for the machine_name is not allowed any more
(since 1.4.8 I think). You have to use the text returned from the
"hostname" command, which, ideally, should be same as the FQDN of your
host server.
I think my FAQ's got some more info on this www.fubra.com/vsdfaq/
HTH,
Ben Kennish
[EMAIL PROTECTED]
www.fubra.com
----- Original Message -----
From: "Matt Andreko" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 09, 2001 2:37 PM
Subject: Re: test environment
Ok, I have this setup. I installed the software, according to the
install directions.
However, when i try doing "vsdadm vs_create machine_name new_alias
ip_address new_domain 200 0 default" it does not work...
i actually setup my /etc/hosts file to make a pseudo-dns system, so that
i can make the example's vsone.net point to 192.168.1.200
I keep getting "connection to localhost could not be established:
Connection refused"
so i looked at /etc/rc.d/init.d/vsd
it's started, but it says it's lockd by subsys...
Any help?
----- Original Message -----
From: Tim Sellar
To: [EMAIL PROTECTED]
Sent: Thursday, August 09, 2001 5:25 AM
Subject: RE: test environment
If your test server is in the same physical location as you are, just
set give it a private IP address (192.168.10.10) and create various
virtual servers (192.168.10.11 - 19), ensure your laptop is also in the
192.168.10.x range on a free IP and you will be away. However, I am
assuming that your test server is in a different physical location to
you and this makes the above option impossible...
If your test server has a true internet IP and you are accessing it
over the web then all of your hosting servers would need true internet
IPs for you to be able to access them directly via HTTP,FTP,SMTP over
the web as well. If you allocate your virtual servers private IP
addresses they would only be visible from the hosting server (though you
may need to modify the hosting server's route table to ensure this) and
not directly from your 'remote' laptop. This should be sufficient to
allow you to try out freeVSD to a limited extent. You can log into your
hosting server and use command-line tools to examine the virtual servers
and most of their services. Use ftp,lynx,telnet etc....I suspect though
that getting mail to work in this context may be a little complicated...
If this proves insufficient, drop me line as our 'demo-svr' full of
virtual server's for people to peruse although still beta may prove
useful.
Tim
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Matt Andreko
Sent: 07 August 2001 16:08
To: [EMAIL PROTECTED]
Subject: test environment
I'm new to the freevsd thing, I just saw it. I'm setting up a test
server to see if it's what i've been looking for. I don't have access
to more than 1 IP at the current location. If i decide to go with
freevsd then i'll have a multitude of them. For my test server, would
it be possible to take my 1 IP, and then assign all the servers to
private IP addresses (192.168.1.x) ? Then i could connect my laptop to
the network, and browse the sites i setup as tests, and administer it.
Would this be a possible testing solution for me?
--
Matt Andreko
On-Ramp Indiana
(317)774-2100
------------------------- 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
-----------------------------------------------------------------------------
