Thanks for the info. I will leave the decision what to do with
mod_chroot (update docs or remove from sid/squeeze) to its maintainer.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>From Stefan Fritsch:
>
> If mod_chroot is not compatible with squeeze's apache, we should
> have it removed from squeeze. Did everything work after you
> removed mod_chroot? Did you have to adjust the configuration?
>
Let me explain what happened. With mod_chroot, the apache did the
chroot tw
On Thursday 07 April 2011, stephan.g...@t-online.de wrote:
> >From Stefan Fritsch:
> > The apache2 core includes now a "Chroot" directive which probably
> > clashes with mod_chroot. Please try without mod_chroot. It is
> > possible that you may have to adjust your configuration, please
> > see the
>From Stefan Fritsch:
>
> The apache2 core includes now a "Chroot" directive which probably
> clashes with mod_chroot. Please try without mod_chroot. It is possible
> that you may have to adjust your configuration, please see the apache2
> docs. I am not familiar with mod_chroot myself.
>
Ah yes
On Monday 04 April 2011, Stephan Goll wrote:
> 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 di
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
6 matches
Mail list logo
