[gentoo-server] apache chroot

[gentoo-server] apache chroot

[Donatas]

Hi,

I'm trying to make mod_cheroot work with apache2.

# mkdir -p /var/www/localhost/htdocs/var/run
# chown -R root.root /var/www/localhost/htdocs/var/run
# ln -s /var/www/localhost/htdocs/var/run/apache2.pid /var/run/apache2.pid



the main features of httpd.conf:

PidFile /var/run/apache2.pid
ChrootDir /var/www/localhost/htdocs
DocumentRoot /

<Directory />
     AllowOverride None
     Options MultiViews FollowSymLinks
#   <IfModule mod_access.c>
#   Order allow,deny
#   Allow from all
#   </IfModule>
     <Limit GET OPTIONS>
       Order allow,deny
       Allow from all
     </Limit>
     <LimitExcept GET OPTIONS>
       Order deny,allow
       Deny from all
     </LimitExcept>
</Directory>




/etc/apache2/modules.d/15_mod_chroot.conf:

<IfDefine CHROOT>
         LoadModule chroot_module modules/mod_chroot.so
</IfDefine>

<IfModule mod_chroot.c>
         # change this to the web root
         ChrootDir /var/www/localhost/htdocs
</IfModule>


/etc/conf.d/apache2

APACHE2_OPTS="-D USERDIR -D DEFAULT_VHOST -D PHP5 -D SSL -D 
SSL_DEFAULT_VHOST -D CHROOT"



After this chroot methot, apache2 starts, but pages cannot be shown. 
Time-out.
This happens, when -D CHROOT is added to /etc/conf.d/apache2


What's the problem? Maby somebody has working mod_chroot?
-- 
gentoo-server@gentoo.org mailing list

Re: [gentoo-server] apache chroot

[Robert Welz]

Donatas wrote:
> Hi,
> 
> I'm trying to make mod_cheroot work with apache2.
> 
> # mkdir -p /var/www/localhost/htdocs/var/run
> # chown -R root.root /var/www/localhost/htdocs/var/run
> # ln -s /var/www/localhost/htdocs/var/run/apache2.pid /var/run/apache2.pid
> 
> 
> 
> the main features of httpd.conf:
> 
> PidFile /var/run/apache2.pid
> ChrootDir /var/www/localhost/htdocs
> DocumentRoot /
> 
> <Directory />
>     AllowOverride None
>     Options MultiViews FollowSymLinks
> #   <IfModule mod_access.c>
> #   Order allow,deny
> #   Allow from all
> #   </IfModule>
>     <Limit GET OPTIONS>
>       Order allow,deny
>       Allow from all
>     </Limit>
>     <LimitExcept GET OPTIONS>
>       Order deny,allow
>       Deny from all
>     </LimitExcept>
> </Directory>
> 
> 
> 
> 
> /etc/apache2/modules.d/15_mod_chroot.conf:
> 
> <IfDefine CHROOT>
>         LoadModule chroot_module modules/mod_chroot.so
> </IfDefine>
> 
> <IfModule mod_chroot.c>
>         # change this to the web root
>         ChrootDir /var/www/localhost/htdocs
> </IfModule>
> 
> 
> /etc/conf.d/apache2
> 
> APACHE2_OPTS="-D USERDIR -D DEFAULT_VHOST -D PHP5 -D SSL -D 
> SSL_DEFAULT_VHOST -D CHROOT"
> 
> 
> 
> After this chroot methot, apache2 starts, but pages cannot be shown. 
> Time-out.
> This happens, when -D CHROOT is added to /etc/conf.d/apache2
> 
> 
> What's the problem? Maby somebody has working mod_chroot?


mine works:
less modules.d/15_mod_chroot.conf:

<IfDefine CHROOT>
         LoadModule chroot_module modules/mod_chroot.so
</IfDefine>

<IfModule mod_chroot.c>
         # change this to the web root
         ChrootDir /var/www
</IfModule>

and /etc/apache2/vhosts.d/00_default_vhost.conf:
<IfDefine DEFAULT_VHOST>
<VirtualHost *:80>
     #
     # DocumentRoot: The directory out of which you will serve your
     # documents. By default, all requests are taken from this 
directory, but
     # symbolic links and aliases may be used to point to other locations.
     #
     DocumentRoot "/localhost/htdocs"

     #
     # This should be changed to whatever you set DocumentRoot to.
     #
     <Directory "/localhost/htdocs">

         #
         # Possible values for the Options directive are "None", "All",
         # or any combination of:
         #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch 
ExecCGI MultiViews
         #

There are several directories under /var/www which might be needed if 
you use php or locales or date and time...

You find it with google or at the mod_php homepage.

Robert
-- 
gentoo-server@gentoo.org mailing list

[gentoo-server] gcc 4.1.1 and glibc 2.4 on amd64

[Tomek Lutelmowski]

Hello,

I would like to upgrade my gentoo production server (AMD64 2006.1/no-multilib 
profile, hardened kernel,gcc and glibc). Do you have any issues regarding 
this upgrade on AMD64 platform? What should I upgrade first - GCC or GLIBC? 
If something goes wrong, quickpkg & emerge of gcc and glibc would help? 

Regards,
Tomek
-- 
gentoo-server@gentoo.org mailing list

Re: [gentoo-server] gcc 4.1.1 and glibc 2.4 on amd64

[Patrick Lauer]

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

On Fri, 2006-09-01 at 09:48 +0200, Tomek Lutelmowski wrote:
> Hello,
> 
> I would like to upgrade my gentoo production server (AMD64 2006.1/no-multilib 
> profile, hardened kernel,gcc and glibc). Do you have any issues regarding 
> this upgrade on AMD64 platform? 
No, that should just work. 

> What should I upgrade first - GCC or GLIBC? 
I think upgrading GCC first is better as that is what the dependencies
suggest (unless I'm still asleep and mixing up things again ;-) )

> If something goes wrong, quickpkg & emerge of gcc and glibc would help? 
Depends - I'd expect glibc to not compile or just work, broken installed
glibc is rather unlikely.
I have just done the same upgrade, even emerge -e world is running well
(and almost finished)

If it really is a production server that can't have downtime you should
test all updates on a second machine that has the exact same software
configuration, that way only your test box dies if anything ever goes
wrong.

Good luck,

Patrick
-- 
Stand still, and let the rest of the universe move

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]