actually for some reason 1725 is not open, but 1726 is...
----- Original Message -----
From: "Tim Sellar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 09, 2001 10:41 AM
Subject: RE: test environment
> Don't do anything with the vsd daemon. VSD operates via inetd (or xinetd)
so
> leave /etc/rc.d/init.d/vsd alone. Use 'netstat -nl' to determine if
anything
> is listening on port 1725 (the VSD port). If it is not, and inetd is
running
> with the latest coinfiguration (use 'killall -HUP inetd' to force it
reread
> its configuration) you may have a faulty entry in /etc/inetd.conf - check
> your /var/log/messages for errors following yuor killall command.
>
> You should have the following at the end of /etc/inetd.conf:
>
> ftp stream tcp nowait root /usr/sbin/virtuald tcpd
/usr/sbin/proftpd -d -l
> telnet stream tcp nowait root /usr/sbin/virtuald tcpd /usr/sbin/in.telnetd
> pop-3 stream tcp nowait root /usr/sbin/virtuald tcpd /usr/sbin/in.qpopper
> #pop-3 stream tcp nowait root /usr/sbin/virtuald tcpd
> /usr/sbin/vm-pop3d -i --group admin --user mail --debug=5
> smtp stream tcp nowait root /usr/sbin/virtuald tcpd /usr/sbin/sendmail -bs
> vsd stream tcp nowait root /usr/sbin/virtuald tcpd /usr/sbin/vsd
> svsd stream tcp nowait root /usr/sbin/virtuald tcpd /usr/sbin/vsd
>
> A particular thing to check is that the path to virtuald is correct (this
> path varies between RPM and source installations and often causes
confusion
> when people move between source and RPM-based installations).
>
> Let me know when you have got something listening on port 1725 and we can
> take it from there...
>
> Tim
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Matt Andreko
> > Sent: 09 August 2001 16:08
> > To: [EMAIL PROTECTED]
> > Subject: Re: test environment
> >
> >
> > ok, i installed using the suggested files, the main rpm, and the bz2
file.
> >
> > however doing a ps -A does not show anything starting with vs....
> > i checked
> > all the paths in /etc/rc.d/init.d/vsd
> >
> > if i restart the vsd daemon it sits for a minute, and doesn't display
any
> > output, and then returns to the shell...
> >
> >
> > ----- Original Message -----
> > From: "Ben Kennish" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, August 09, 2001 10:00 AM
> > Subject: Re: test environment
> >
> >
> > > Well we can't have a reader of my FAQ in any problems now can we.. :-)
> > >
> > > I shouldn't worry about /etc/rc.d/init.d/vsd status reporting that
> > > subsys locked stuff. It's basically doing a "ps -A", seeing that the
> > > "vsd" process isn't running and assuming this is a problem (which it
> > > isn't - I get this message on a server in regular use in the office.)
> > >
> > > Have you compiled with SSL support?
> > >
> > > If you do an /etc/rc.d/init.d/vsd restart, do you see anything
> > > happening. If not, u might need to check out the /etc/rc.d/init.d/vsd
> > > file and make sure that it's pointing at the correct location for the
> > > binaries (something I don't think it does after a source install.)
> > >
> > > Oh and if you do "ps -A", do you see any "vsdredirect" processes?
> > >
> > > HTH,
> > >
> > >
> > > Ben Kennish
> > > [EMAIL PROTECTED]
> > > www.fubra.com
> > >
> > > ----- Original Message -----
> > > From: "Matt Andreko" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Thursday, August 09, 2001 3:18 PM
> > > Subject: Re: test environment
> > >
> > >
> > > actually, that's what I've been reading. I put in my /etc/hosts file:
> > > 192.168.1.100 mandreko2.com
> > > 192.168.1.200 vsone.net
> > >
> > > and did
> > > vsdadm vs_create mandreko2.com vsone 192.168.1.200 vsone.net 200 0
> > > default
> > >
> > > but i still get "connection to host....."
> > > i don't see anything in /var/log/messages other than it saying the
> > > command
> > > didn't work... no info from inetd.
> > > ----- Original Message -----
> > > From: "Ben Kennish" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Thursday, August 09, 2001 8:56 AM
> > > Subject: Re: test environment
> > >
> > >
> > > > 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
> > >
> ----------------------------------------------------------------------
> > > ----
> > > ---
> > >
> > > ------------------------- 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
> >
> ------------------------------------------------------------------------
> > > -----
> > >
> > > ------------------------- 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
>
> --------------------------------------------------------------------------
> ---
>
> ------------------------- 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
> --------------------------------------------------------------------------
--
> -
>
> ------------------------- 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
> --------------------------------------------------------------------------
---
------------------------- 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
-----------------------------------------------------------------------------
