Standardising the naming of the package files (in just such a manner) is planned. However it has not been a priority for two reasons: 1. If the instructions are followed correctly, it isn't an issue. 2. We are in the process of phasing out most of the vsd-specific packages as they add unnecessary complexity and result in an awful lot of queries on the support lists. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of C Neale > Sent: 21 March 2001 13:46 > To: [EMAIL PROTECTED] > Subject: Re: Fundamental error : vsdredirect listens on host server IP > > > perhaps the vsd rpms should carry a "-vsd-1.4.x" suffix? > > ----- Original Message ----- > From: "Tim Sellar" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, March 21, 2001 11:10 AM > Subject: RE: Fundamental error : vsdredirect listens on host server IP > > > > You seem to be getting into a right old pickle. I suggest you > rebuild you > > skel (having stopped and deleted your existing virtual servers). Before > you > > build the skel ensure the vsd glib rpms are in > /usr/share/freevsd/pkgs and > > that the following line is present the the end of /etc/freevsd.conf: > > > > $add_ons = '/usr/share/freevsd/pkgs'; > > > > > > This line will not be present if you installed the freevsd-pkgs > rpm prior > to > > installing the freevsd rpm. > > > > Tim > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]On Behalf Of C Neale > > > Sent: 20 March 2001 18:26 > > > To: [EMAIL PROTECTED] > > > Subject: Re: Fundamental error : vsdredirect listens on host server IP > > > > > > > > > I did upgrade the glibc version on the host server, but the > VSs _should_ > > > have the freevsd patched version from freevsd-pkgs-1.4.6-rh71.i386.rpm > > > > > > There must be some hiccup when the skel is created? > > > > > > My server is a fresh-ish install; I have reiserfs for my /home > partition, > > > which I accomodate with a kernel rpm for Mdk 7.2 > > > > > > Chris Neale > > > > > > ----- Original Message ----- > > > From: "Tim Sellar" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Tuesday, March 20, 2001 9:34 AM > > > Subject: RE: Fundamental error : vsdredirect listens on host server IP > > > > > > > > > > The patched version of glibc used within virtual servers causes the > > > hostname > > > > comand to return the hostname contained in /etc/FQDN. If when > > > you run the > > > > hostname command within a VS the host server name is returned > > > you probably > > > > have un-patched glibc installed in your skel (you should also see a > > > problem > > > > in your command line prompt) > > > > > > > > Tim > > > > > > > > > -----Original Message----- > > > > > From: [EMAIL PROTECTED] > > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of > Matt Kennedy > > > > > Sent: 20 March 2001 03:50 > > > > > To: [EMAIL PROTECTED] > > > > > Subject: Re: Fundamental error : vsdredirect listens on > host server > IP > > > > > > > > > > > > > > > On 19 Mar 2001 21:20:43 +0000, C Neale wrote: > > > > > > The line in /home/vsd/vs/*/etc/rc : > > > > > > > > > > > > IP_ADDR=`hostname -i ...` > > > > > > > > > > > > seems to use the ip of the host server (provided it has a DNS > > > > > entry - if not there's a host unresolved error) > > > > > > > > > > > > On one occasion there were two instances of vsdredirect per > > > > > virtual server; however, before then and since if there is more > > > > > than one there are bind() errors because vsdredirect using the > > > > > aforementioned line in rc is trying to map 80 to 8080 per vs but > > > > > always using the host server's ip > > > > > > > > > > > > the hostname -i part looks for black-footed.local. > > > > > > > > > > > > The way I have got round it is to specify the IP in place > > > of the line: > > > > > > IP_ADDR=`hostname -i ...` > > > > > > > > > > > > I put: > > > > > > IP_ADDR=10.0.0.1 # forexample > > > > > > > > > > > > Why does the vsd system use the wrong hostname ? > > > > > > > > > > It doesn't. The process that executes the boot scripts > for the vs is > > > > > chroot()'ed into the vs when that script executes. The result of > > > > > hostname -i will be different as a result. Run the hostname -i > command > > > > > on the base server and on a working vs and you should see a > different > > > > > address for each. > > > > > It's possible that the configuration on the offending vs has > > > been munged > > > > > in some way that causes the hostname command to return the wrong > info. > > > > > I've had this happen before when madly banging on freevsd cvs > > > snapshots > > > > > and not paying attention to what I was doing. > Unfortunately, I just > > > > > hosted the vs and rebuilt it, so I'm not sure offhand which > > > config files > > > > > on the vs that you should check to correct hostname's output. > > > > > > > > > > > > > > > -- > > > > > Matt Kennedy > > > > > Programmer Jumpline.com, Inc. > > > > > > > > > > > >
