Re: Question about permissions used on onconfig and sqlhosts files

Andrew Hamm wrote: > Colin Bull wrote: > >>Having just gone through the routine of installing 9.4 without >>overwriting 7.31, I just wish this advice had been followed >>earlier. We live and learn. There is only so much you can do >>with symbolic links. > > > Very true; I'm keen to try a bit of chrooting too. > > My latest fashion for production installs is to put each product in > /SOMEWHERE/informix.731 (for example) and THEN setup a symlink from > /SOMEWHERE/informix pointing to the current production install. This way, a > fall-back is as simple as re-pointing the symlink (oh, and the engine > upgrade rollback). This approach also means that precicely zero scripts need > editing to change the value of $INFORMIXDIR. I've always done it this way. When you do an upgrade it means you don't lose the old version if you need to revert back. It also allows you to have a sensible directory name in onconfig, and allows you to do a clean install when upgrading. So any spurious files in your $INFORMIXDIR 'disappear' when you drop and recreate the link. ;-) > If you need more than one engine in production, then it's still reasonable > to have a few symlinks such as /SOMEWHERE/informix.prod, > /SOMEWHERE/informix.web, /SOMEWHERE/informix.dw, and make them point to the > appropriate install directory; once again, saving the need to edit any > scripts or config files. > > I find this plan is less effective for development machines, because we > often want multiple engines running simultaneously for either testing or > pragmatic reasons. However, we've got shell functions which flip shell > variables all over the place, even automatically just by performing a cd, so > that different style in development works well. Yup, I've got scripts that change environment for you and tell you which env you are using. Some of them even tell you if you haven't sourced them correctly. This is also useful in development for testing apps against different versions of the DB server. Just bring the DB server down, flip the link and bring the DB server up again. Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /| | Mydas Solutions Ltd http://MydasSolutions.com |///// / //| | +-----------------------------------+//// / ///| | |We value your comments, which have |/// / ////| | |been recorded and automatically |// / /////| | |emailed back to us for our records.|/ ////////| +----------------------+-----------------------------------+-----------+ sending to informix-list