I can confirm that Chroot is working in the proposed (2.4.6-2ubuntu2.1 )
Thank you for the fix.
-Arul
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails
Any update on when can we get a fix for this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot when not started as root error
To
Thank you for reviewing this bug report and assigning the severity.
While I agree with you on the assigned severity of Medium, I'd like
to point out that though ChrootDir is not a default option, it relates
to the security of apache server. I am not sure how many users simply
use the server w/
Public bug reported:
I have set my chroot directory as shown below.
ChrootDir /var/www
When started with the above chroot setting, apache2 exits with the
following error
[Sat Nov 16 13:52:40.621872 2013] [unixd:alert] [pid 3747] (34)Numerical
result out of range: AH02158: Cannot chroot when
Brian, thanks for the explanation, I had the same issue after upgrade to
Precise and its all good now after removing the old/duplicate rules as
per your suggestion!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
