httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 51371] wrong guards around 'apr_procattr_limit_set' in mod_cgi.c
Date Fri, 17 Jun 2011 21:37:52 GMT

Anthony Foiani <> changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |NEW

--- Comment #2 from Anthony Foiani <> 2011-06-17 21:37:52 UTC
(In reply to comment #1)
> Can you post config.log from APR where RLIMIT_* was defined but APR autoconf
> decided to not set APR_HAVE_STRUCT_RLIMIT?   And where "struct rlimit" is
> defined in your system?

It's a bit messy, as I'm cross-compiling: building on linux (Fedora 14 x86_64)
for a powerpc linux target.

As such, I'm running the httpd (and hence apr) config machinery against the
cross-compiler and the kernel headers for the target system, not my local

I'll see if I can't reproduce the problem, but I have been in "fix and move on
mode" since I reported this issue, so getting back to that exact configuration
might be difficult.  My actual configuration stanza is as follows; the extra
variables are there to keep the configuration script from trying to run target
binaries on the host.

    ac_default_prefix=/                                 \
    ac_cv_sizeof_struct_iovec=8                         \
    ac_cv_struct_rlimit=yes                             \
    ac_cv_define_PTHREAD_PROCESS_SHARED=yes             \
    ac_cv_func_setpgrp_void=yes                         \
    ac_cv_file__dev_zero=yes                            \
    ac_site_file=NONE                                   \
    ap_cv_void_ptr_lt_long=no                           \
    apr_cv_tcp_nodelay_with_cork=yes                    \
    apr_cv_mutex_robust_shared=yes                      \
    apr_cv_process_shared_works=yes                     \
    manualdir=/doc/httpd-manual                         \
    ./configure                                         \
        --prefix=/                                      \
        --sysconfdir=/etc                               \
        --datadir=/www                                  \
        --docdir=/doc                                   \
        --host="$TARGET_TUPLE"                          \
        --enable-auth-digest                            \
        --enable-deflate --with-z="$PLATFORM_STAGE"     \
        --enable-expires                                \
        --enable-headers                                \
        --enable-logio                                  \
        --enable-ssl=no                                 \
      || exit 1

> (I assume that's what cgi is relying on)

I'm not sure how to describe the "relies on" relationship any better than in my
original problem description: threadproc uses one guard to determine whether it
should provide a particular function, while mod_cgi uses a different guard to
determine whether it should call said function.

It's clear that mod_cgi doesn't *need* this call; it will still work even
without it, but it just won't enforce resource limits on child processes.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message