Re: [MLUG] Cohabitating Apaches and YUM woes

[Michael <EMAIL:PROTECTED>]

Just FYI. You can avoid a lot of these problems by custom compiling 
services and not letting them install in the usual places. I like to 
install them in their own user accounts which I put under /services 
(rather than /home). So for example /services/apache and 
/services/apache2. I like this because it makes it easy to manage (su - 
apache) while keeping all the related files in one place. This way I can 
even throw the logrotate scripts, cron jobs, etc related to managing the 
services into the same repository of files and find them easily. I 
create links, as needed, from the usual locations for these programs to 
where I've installed them. This should keep most nasty interactions 
between different versions from happening as well as keeping packaged 
files from overwriting anything. Of course it makes backing up those 
files a snap too as you can backup all your services as easily as 
running 'find' for files that've changed under /services and tarballng 
them up. I do that hourly. I also keep install scripts for each of these 
services so I can usually reinstall as easy as wiping the old files, 
downloading the new tarballs, and typing './install'. It's an easy step 
to take after installing for the first time that'll save you a lot of 
hassle when maintaining your services.

For those who might be interested.. I also create users for each virtual 
host I have and put their files in /domains. So for kavlon.com I'd put 
the web files in /domains/kavlon/www. Again this makes management really 
easy especially if you're dealing with hundreds or thousands of domains.


-- 
Michael <EMAIL:PROTECTED>
http://kavlon.org

_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members