From owner-freebsd-questions@FreeBSD.ORG Mon Jun 20 14:12:01 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36C761065670 for ; Mon, 20 Jun 2011 14:12:01 +0000 (UTC) (envelope-from jacks@sage-american.com) Received: from mail.sagedata.net (mail.sagedata.net [38.106.15.121]) by mx1.freebsd.org (Postfix) with ESMTP id 068F98FC15 for ; Mon, 20 Jun 2011 14:12:00 +0000 (UTC) Received: from SAGEPLACE (99-111-143-27.lightspeed.crchtx.sbcglobal.net [99.111.143.27]) by mail.sagedata.net (8.14.5/8.14.5) with SMTP id p5KEBxZp028030; Mon, 20 Jun 2011 09:12:00 -0500 (CDT) (envelope-from jacks@sage-american.com) X-Authentication-Warning: mail.sagedata.net: Host 99-111-143-27.lightspeed.crchtx.sbcglobal.net [99.111.143.27] claimed to be SAGEPLACE Message-Id: <3.0.1.32.20110620091159.0198ccf8@sage-american.com> X-Sender: jacks@sage-american.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Mon, 20 Jun 2011 09:11:59 -0500 To: Michael Powell , freebsd-questions@freebsd.org From: "Jack L. Stone" In-Reply-To: References: <64D6EF8B-A799-4D8C-A688-FC020CCFEFD1@d3photography.com> <3.0.1.32.20110615175738.019581f8@sage-american.com> <3.0.1.32.20110615155910.019581f8@sage-american.com> <3.0.1.32.20110615150619.019581f8@sage-american.com> <3.0.1.32.20110615090401.0181fea8@sage-american.com> <3.0.1.32.20110615090401.0181fea8@sage-american.com> <3.0.1.32.20110615150619.019581f8@sage-american.com> <3.0.1.32.20110615155910.019581f8@sage-american.com> <3.0.1.32.20110615175738.019581f8@sage-american.com> <3.0.1.32.20110615191858.018e54e0@sage-american.com> <64D6EF8B-A799-4D8C-A688-FC020CCFEFD1@d3photography.com> <85B7376289F04B2596EBE3090DB9D970@rivendell> <3.0.1.32.20110616085819.018c54e0@sage-american.com> <0122428124834D73AAE4EE5178CEE27C@rivendell> <3.0.1.32.20110616105844.027f64f8@sage-american.com> <3.0.1.32.20110616144533.0196a408@sage-american.com> <3.0.1.32.20110617192644.03caff20@38.106.15.121> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Greylist: Message whitelisted by Sendmail access database, not delayed by milter-greylist-4.2.7 (mail.sagedata.net [38.106.15.121]); Mon, 20 Jun 2011 09:12:00 -0500 (CDT) X-Scanned-By: milter-spamc/1.15.388 (mail.sagedata.net [38.106.15.121]); Mon, 20 Jun 2011 09:12:00 -0500 X-Spam-Status: NO, hits=-10.00 required=4.50 X-Spam-Report: Content analysis details: (-10.0 points, 4.5 required) | | pts rule name description | ---- ---------------------- -------------------------------------------------- | -0.0 SHORTCIRCUIT Not all rules were run, due to a shortcircuited rule | -10 ALL_TRUSTED Passed through trusted hosts only via SMTP | Cc: Subject: Re: Another PHP5 problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2011 14:12:01 -0000 At 06:49 PM 6/17/2011 -0400, Michael Powell wrote: >Jack L. Stone wrote: > >[snip out a lot] >> >> What did you fellows do about this issue that worked best for you assuming >> y'all had vhosts and similar stuff to worry about? > >Me I just bit the bullet and went with the new locations as they were >installed as defaults. I moved my content to the location. None of my >content cared about the underlying file system path, however there is code >that does. When faced with this most of the time there is some configuration >utility that can be run to make changes, with the actual data you enter >being stored in a database backend. This then becomes a choice of "is it >easier to simply modify the docroot in the .conf files?", if you have this >situation. > > >-Mike > Just a follow-up on my own experience with upgrade to apache22 and its change of path. I was just overthinking it. Simply changing the doc root in the main httpd conf to match my exising one worked beautifully with any concern about moving content around and breaking the system path for scripts and things. By modifying the www/apache22/data back to www/data left everything as was. My production servers are now updated this way. My web serving was only down for a few minutes as I left apache2 running in memory. I simply uploaded copies of all of my tested .conf files from the test server before installing apache22. Also first made the minor changes needed to the main conf and vhost.conf. Killed the apache2 and voila! Thanks for your version of the process, but thought I'd post mine here too just in case there is anyone left on the planet besides me that hasn't already upgraded to apache22. Truly it doesn't pay to get too far behind on upgrades.... (^_^) Happy trails, Jack L. Stone System Admin Sage-american