[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#620759: apache2: apache does chroot twice with mod_chroot



Package: apache2.2-common
Version: 2.2.16-6+squeeze1
Severity: normal


I have apache2 running chrooted in /var/www since lenny. After upgrading 
to squeeze I got permanent errors about not finding /var. After all I 
tried and copied and hoped to find it out and finally I created a var in 
/var/www/var/www and apache did not complain anymore. So I guess the 
apache father does chroot into /var/www and every child does chroot 
into the chrootet /var/www again (and this is really /var/www/var/www). 
This is really strange and surely a bug.
Best regards,
Stephan

-- Package-specific info:
List of enabled modules from 'apache2 -M':
  alias auth_basic authz_default authz_host autoindex chroot deflate
  dir env mime negotiation reqtimeout setenvif status

-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'oldstable')
Architecture: i386 (i586)

Kernel: Linux 2.6.26
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages apache2 depends on:
ii  apache2-mpm-worker     2.2.16-6+squeeze1 Apache HTTP Server - high speed th
ii  apache2.2-common       2.2.16-6+squeeze1 Apache HTTP Server common files

apache2 recommends no packages.

apache2 suggests no packages.

Versions of packages apache2.2-common depends on:
ii  apache2-utils          2.2.16-6+squeeze1 utility programs for webservers
ii  apache2.2-bin          2.2.16-6+squeeze1 Apache HTTP Server common binary f
ii  libmagic1              5.04-5            File type determination library us
ii  lsb-base               3.2-23.2squeeze1  Linux Standard Base 3.2 init scrip
ii  mime-support           3.48-1            MIME files 'mime.types' & 'mailcap
ii  perl                   5.10.1-17         Larry Wall's Practical Extraction 
ii  procps                 1:3.2.8-9         /proc file system utilities

-- no debconf information



Reply to: