i'm searching about to ameliorate chroot funciton of "mod_chroot" and "mod_security" module to be working normaly with apache reload.
the probleme is that the chroot occure in apache main processes who control child forking...
and not in the start of the child (after the fork)...
because of that the chroot are permanante... and the apache main process canot be abel to reload configuration file that are outside of the chroot...
my first idea is to make chroot in child_init hook in place of post_config... but...they dont work...
and when have analysed the apache code have found why no working:
the child_init hook occure after the setuid (unixd_setup_child) and after that is not possible to make chroot beceause at this point dont have the nessery right to do that...
my question is how to make possible root action in child init phase?
displacing the hook before "unixd_setup_child" ? but what is the impact of this ?
adding a other hook placed before "unixd_setup_child" ?
i'm interested of idea to resolve this!
Thanks,
Mathieu
From: Eric Covener [mailto:[EMAIL PROTECTED]
To: [email protected]
Sent: Fri, 20 Oct 2006 13:30:12 +0200
Subject: [EMAIL PROTECTED] Re: module that doesn't want to be shared.
On 10/20/06, Jean-frederic Clere <[EMAIL PROTECTED]> wrote:
> On Fri, 2006-10-20 at 11:53 +0200, Jean-frederic Clere wrote:
> > Hi,
> >
> > I have added a modules to httpd-trunk but I have not able to get it
> > shared. (modules.mk shared = is empty!).
>
> I have removed my copy of the repos, checkout again copy back my module
> files. And now it works.
FWIW I've seen this happen if you have a 2nd copy of a module
directory (as in cp -r modules/debug modules/debug.bak) in your
source tree.
--
Eric Covener
[EMAIL PROTECTED]
