RE: [ilugd] Apache 1.3x on pCQ 7.1
Add /usr/intranet to DocumentRoot, apache looks for alias folders under DocumentRoot -js $ Alias /intranet/ /usr/intranet/ $ Directory /usr/intranet $ Options Indexes FollowSymlinks MultiViews $ AllowOverride None $ Order allow,deny $ Allow from all $ /Directory $ ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] Apache 1.3x on pCQ 7.1
but I want to keep /var/www/html as dcoument root, and still access the intranet directory as http://webservername/intranet Do I have to create a virtual host? or should I create a Sym link to /usr/intranet in the /var/www/html directory - Original Message - From: Jasmeet S. Virdi [EMAIL PROTECTED] To: 'The Linux-Delhi mailing list' [EMAIL PROTECTED] Sent: Wednesday, September 24, 2003 12:20 PM Subject: RE: [ilugd] Apache 1.3x on pCQ 7.1 Add /usr/intranet to DocumentRoot, apache looks for alias folders under DocumentRoot -js $ Alias /intranet/ /usr/intranet/ $ Directory /usr/intranet $ Options Indexes FollowSymlinks MultiViews $ AllowOverride None $ Order allow,deny $ Allow from all $ /Directory $ ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
RE: [ilugd] Apache 1.3x on pCQ 7.1
Don't delete /var/www/html from DocumentRoot, let it remain; also ADD the new folder as DocumentRoot. Also take a look at http://httpd.apache.org/docs/mod/core.html#documentroot and http://httpd.apache.org/docs-2.0/mod/mod_alias.html -js $ -Original Message- $ From: [EMAIL PROTECTED] $ [mailto:[EMAIL PROTECTED] $ g] On Behalf Of Mani $ Sent: Wednesday, September 24, 2003 1:14 PM $ To: The Linux-Delhi mailing list $ Subject: Re: [ilugd] Apache 1.3x on pCQ 7.1 $ $ $ but I want to keep /var/www/html as dcoument root, and still $ access the intranet directory as http://webservername/intranet $ $ Do I have to create a virtual host? or should I create a Sym $ link to /usr/intranet in the /var/www/html directory $ - Original Message - $ From: Jasmeet S. Virdi [EMAIL PROTECTED] $ To: 'The Linux-Delhi mailing list' [EMAIL PROTECTED] $ Sent: Wednesday, September 24, 2003 12:20 PM $ Subject: RE: [ilugd] Apache 1.3x on pCQ 7.1 $ $ $ Add /usr/intranet to DocumentRoot, apache looks for alias folders $ under DocumentRoot $ $ $ -js $ $ Alias /intranet/ /usr/intranet/ $ $ Directory /usr/intranet $ $ Options Indexes FollowSymlinks MultiViews $ $ AllowOverride None $ $ Order allow,deny $ $ Allow from all $ $ /Directory $ $ $ $ $ ___ $ ilugd mailing list $ [EMAIL PROTECTED] $ http://frodo.hserus.net/mailman/listinfo/ilugd $ $ $ $ ___ $ ilugd mailing list $ [EMAIL PROTECTED] $ http://frodo.hserus.net/mailman/listinfo/ilugd $ ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] Apache 1.3x on pCQ 7.1
how can there be two document root's? Is it possible? The link you refered to just explain how to set a document root and an Alias. Nothing about having 2 seperate document roots.. I think you can have only one document root per host - Original Message - From: Jasmeet S. Virdi [EMAIL PROTECTED] To: 'The Linux-Delhi mailing list' [EMAIL PROTECTED] Sent: Wednesday, September 24, 2003 2:11 PM Subject: RE: [ilugd] Apache 1.3x on pCQ 7.1 Don't delete /var/www/html from DocumentRoot, let it remain; also ADD the new folder as DocumentRoot. Also take a look at http://httpd.apache.org/docs/mod/core.html#documentroot and http://httpd.apache.org/docs-2.0/mod/mod_alias.html -js $ -Original Message- $ From: [EMAIL PROTECTED] $ [mailto:[EMAIL PROTECTED] $ g] On Behalf Of Mani $ Sent: Wednesday, September 24, 2003 1:14 PM $ To: The Linux-Delhi mailing list $ Subject: Re: [ilugd] Apache 1.3x on pCQ 7.1 $ $ $ but I want to keep /var/www/html as dcoument root, and still $ access the intranet directory as http://webservername/intranet $ $ Do I have to create a virtual host? or should I create a Sym $ link to /usr/intranet in the /var/www/html directory $ - Original Message - $ From: Jasmeet S. Virdi [EMAIL PROTECTED] $ To: 'The Linux-Delhi mailing list' [EMAIL PROTECTED] $ Sent: Wednesday, September 24, 2003 12:20 PM $ Subject: RE: [ilugd] Apache 1.3x on pCQ 7.1 $ $ $ Add /usr/intranet to DocumentRoot, apache looks for alias folders $ under DocumentRoot $ $ $ -js $ $ Alias /intranet/ /usr/intranet/ $ $ Directory /usr/intranet $ $ Options Indexes FollowSymlinks MultiViews $ $ AllowOverride None $ $ Order allow,deny $ $ Allow from all $ $ /Directory $ $ $ $ $ ___ $ ilugd mailing list $ [EMAIL PROTECTED] $ http://frodo.hserus.net/mailman/listinfo/ilugd $ $ $ $ ___ $ ilugd mailing list $ [EMAIL PROTECTED] $ http://frodo.hserus.net/mailman/listinfo/ilugd $ ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] Apache 1.3x on pCQ 7.1
Mani wrote: hi all, I have PCQ 7.1 installed with Apache 1.3.19-6 installed. I need to upgrade this to apache 1.3.27. I have downloaded the rpm's from RH site, but when i try to install the new package, it givemes me failed dependencies errors.. mod_bandwidth is needed by apache-1.3.27-2.7.1 mod_put is needed by apache-1.3.27-2.7.1 mod_throttle is needed by apache-1.3.27-2.7.1 libmm.so.11 is needed by apache-1.3.27-2.7.1 apache = 1.3.19-5 is needed by mod_ssl-2.8.1-5 So I got the above packages, but these conflict with the existing Apache 1.3.19 rpm -ivh mod_bandwidth-2.0.3-2.i386.rpm error: failed dependencies: apache 1.3.22-1 conflicts with mod_bandwidth-2.0.3-2 And I cannot remove the existing apache either as also gives dependecies errors If I compile Apache from source will these dependencies be taken care of? or will apache still need these packages? Ofcourse recompilation will take care of dependencies. But there is one more thing to try. Try to upgrade and install the new apache and the downloaded modules together. You must have been trying to only install the new modules. Try rpm -Uvh apache-* mod* rpm should check and find out that if the old apache has to go then the conflicts dont hold. Do tell me if this or does not work! :) - Sandip -- Sandip Bhattacharyahttp://www.sandipb.net sandip at puroga.com Puroga Technologies Pvt. Ltd. http://www.puroga.com ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] Apache 1.3x on pCQ 7.1
--- Sandip Bhattacharya [EMAIL PROTECTED] wrote: Mani wrote: hi all, I have PCQ 7.1 installed with Apache 1.3.19-6 installed. I need to upgrade this to apache 1.3.27. I have downloaded the rpm's from RH site, but when i try to install the new package, it givemes me failed dependencies errors.. Try rpm -Uvh apache-* mod* I would not recommend that. RedHat has specific rpms for 7.1 For security issues they will probably back port patches to apache 1.3.27 or in extreme cases generate rpm for a newer version. The OP has not mentioned the distribution for which the rpm's were downloaded but if they are for 7.1 it is best if up2date is used and all the dependancies are resolved. If that is not a acceptable option I would rather remove all apache* and mod_* rpm's before building from source. Mithun __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] Apache 1.3x on pCQ 7.1
Actually, I had downloded the RPMS for Red Hat 7.1, I had even tried using up2date. the thing is Red hadt's certificate that's used by up2date to connect to Rh site expired somewhere in august.; so i was facing the same probel truying to upgrade up2date for Rh 7.1 :) , It gave some python-xmlrpc, which inturn asked for mkinitrd 3.2 which inturn. So I decided to compile from source I downloded apache_1.3.28 source, and mod_perl first I compiled apache with the folowing options configured apache with the folowing options ./configure --prefix=/usr/local/apache --enable-module=most--enable-shared=m ax --with-layout=RedHat make make install then i compiled mod=perl withthe following options perl Makefile.PL APACHE_SRC=../apache_1.3.28/src DO_HTTPD=1 USE_APACI=1 It works now... BTW: how do I check for all the modules that are installed with apache? mani - Original Message - From: Sandip Bhattacharya [EMAIL PROTECTED] To: The Linux-Delhi mailing list [EMAIL PROTECTED] Sent: Tuesday, September 23, 2003 12:14 PM Subject: Re: [ilugd] Apache 1.3x on pCQ 7.1 Mithun Bhattacharya wrote: I would not recommend that. RedHat has specific rpms for 7.1 For security issues they will probably back port patches to apache 1.3.27 or in extreme cases generate rpm for a newer version. The OP has not mentioned the distribution for which the rpm's were downloaded but if they are for 7.1 it is best if up2date is used and all the dependancies are resolved. If that is not a acceptable option I would rather remove all apache* and mod_* rpm's before building from source. The OP is definitely more at ease using packages than compiling from source. Atleast with using packages, he will no only need to upgrade from RPMs at apache site from time to time, and not recompile everytime a new version is out. - Sandip P.S. In the times of apt-get you still want to use up2date? ;) Ofcourse yes, apt-repositories for 7.1 does not exist i think. That is one good reason -- Sandip Bhattacharyahttp://www.sandipb.net sandip at puroga.com Puroga Technologies Pvt. Ltd. http://www.puroga.com ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
Re: [ilugd] Apache 1.3x on pCQ 7.1
Mani wrote: BTW: how do I check for all the modules that are installed with apache? httpd -l Doesn't show dynamically loaded modules though. - Sandip -- Sandip Bhattacharyahttp://www.sandipb.net sandip at puroga.com Puroga Technologies Pvt. Ltd. http://www.puroga.com ___ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd