I'm on my knees today. The INSTALL document needs changing, I've recently finished the body to a vsd-upgrade script, and its just going through testing now (available through CVS if you want it now). If you've installed through RPM, the upgrade process couldn't be simpler: vsboot --stop rpm -Uvh <new version of freevsd> vsboot --start Through the marvels of RPMs, the spec file won't be overwritten, so all of your configuration files will remain intact, the virtual servers will remain intact and so on. The only thing that won't get upgraded is the skel, but the old version should tick along nicely. If you wanted the new skel functionality, then install it and move the virtual servers on to it (vsd-linkvs.pl). The skel DOES NOT have to be upgraded it is only advisable/desirable. However, if you are installing from source, you will need to make a copy of both vsd.conf and freevsd.conf as the make rules will overwrite any existing configuration files, but everything else will remain intact. In either case there is no need to run vsd-install.pl (or vsd-uninstall.pl beforehand), just replace your config files (if need be) and away you go. Now the only problems arise if you are using a pre 1.4.8 version, where the configuration file format changed slightly, but the vsd-upgrade.pl script has been designed to make those modifications for you. Estimated time scale for the freeVSD upgrade? I'd say 5 mins, the files that need to be checked are: [/usr/local]/etc/vsd/vsd.conf [/usr/local]/etc/vsd/freevsd.conf If you have a /etc/vsd.conf and /etc/freevsd.conf, then vsd-upgrade.pl needs to be run which will create the vsd dir, copy in the existing conf files, and add the new sections of configuration. To upgrade the virtual servers however, may take a fair while longer. The actual time taken to copy over a virtual server is dependant on far too many things for me to give an estimate. vsd-linkvs.pl will, however, check for differing config files etc in the virtual server, and copy in any that differ from the skel with a .linkupdate suffix as to not overwrite any existing information. I do hope this helps to clear a few things up, and let me know if anything else is unclear, Damion. Oh, I trebble checked everyhting before writing this reply :). redirect wrote: > > following your install doc for upgrading it says: > > 1) stop all the VS's > 2) move the skel > 3) back-up vsd.conf > 4) uninstall freeVSD > 5) install new freeVSD > 6) install a skel > 7) create all the VS's again > 8) transfer the volatile data to the new VS's created > > what's your estimated timescale for this considering say just 40 VS's, 1 > server including picking through /etc to find altered files? Plus we had to > rewrite sendmail.cf to get it to work on 1.4.9 so not sure if that will have > to be done again. Also when we tested an uninstall previously we couldn't > re-install freeVSD until we cleaned off everything and reloaded OS, is this > a possibility? > > where's the documentation for what you have mentioned below for upgrading? > Does upgrading to 1.4.9-2 mean a new skel has to be used? > > ----- Original Message ----- > From: "Damion Parry" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, August 15, 2001 11:19 AM > Subject: Re: Sendmail Problems -- Error > > > Having just checked it out, I must apologise for the following: > > > > > upgrading the RPM in the skel should not be too traumatic, the whole > > > idea of the skel is that you only have to do something once and it will > > > be applied to all virtual servers. As long as there are no new files in > > > the new rpm (ie a file exists in the new RPM and not in the old one, and > > > therefore not in the virtual server), the new versions of each of the > > > existing files will become available to all virtual servers as soon as > > > they are repaced in the skel. > > > > The new version of the rpm will take effect with all new virtual servers > > created, but the old vs's retain the inode of the original file. > > Therefore, the only way to upgrade is via vsd-linkvs.pl. > > > > Sorry, > > Damion. > > ------------------------- 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 -----------------------------------------------------------------------------
