Re: httpd -k start illegal option -- k
Ruediger Pluem wrote: On 03/28/2009 08:11 PM, Mladen Turk wrote: Current trunk gives the $ ./httpd -k start httpd: illegal option -- k Is there some new config directive that needs to be added since mpm redesign, or it's just a temporary bug? I guess it is bug that has something to do with how ap_mpm_rewrite_args is now called. Think that too. Are you running on the latest trunk revision? Yes, but just in case I did a completely clean svn co for httpd and apr trunk $ svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk httpd ... Checked out revision 759642. $ cd httpd $ svn co http://svn.apache.org/repos/asf/apr/apr/trunk srclib/apr ... Checked out revision 759643. $ ./buildconf $ ./configure --with-layout=Apache --prefix=`pwd`/release/linux2 \ --with-included-apr --enable-mods-shared=all --enable-pie \ --enable-proxy --with-port=8000 --with-devrandom=/dev/urandom $ make (no errors, no warnings) $ make install $ cd release/linux2/bin $ ./httpd -k start Same thing (httpd: illegal option -- k) Are u able to run it? Regards -- ^(TM)
Re: httpd -k start illegal option -- k
Ruediger Pluem wrote: $ ./httpd -k start httpd: illegal option -- k Is there some new config directive that needs to be added since mpm redesign, or it's just a temporary bug? I guess it is bug that has something to do with how ap_mpm_rewrite_args is now called. Well they were not called at all. I added the common ap_mpm_rewrite_args hook to mpm modules table, so it runs now. Somehow I wonder if that was Jeff's design idea. Regards -- ^(TM)
Re: httpd -k start illegal option -- k
On 03/29/2009 10:29 AM, Mladen Turk wrote: Ruediger Pluem wrote: $ ./httpd -k start httpd: illegal option -- k Is there some new config directive that needs to be added since mpm redesign, or it's just a temporary bug? I guess it is bug that has something to do with how ap_mpm_rewrite_args is now called. Well they were not called at all. I added the common ap_mpm_rewrite_args hook to mpm modules table, so it runs now. Somehow I wonder if that was Jeff's design idea. Jeff's idea was to move it as in the current design this does not work if the MPM is loaded as a DSO. Regards RĂ¼diger
Re: httpd -k start illegal option -- k
On Sun, Mar 29, 2009 at 6:42 AM, Ruediger Pluem rpl...@apache.org wrote: On 03/29/2009 10:29 AM, Mladen Turk wrote: Ruediger Pluem wrote: $ ./httpd -k start httpd: illegal option -- k Is there some new config directive that needs to be added since mpm redesign, or it's just a temporary bug? I guess it is bug that has something to do with how ap_mpm_rewrite_args is now called. Well they were not called at all. I added the common ap_mpm_rewrite_args hook to mpm modules table, so it runs now. Somehow I wonder if that was Jeff's design idea. Jeff's idea was to move it as in the current design this does not work if the MPM is loaded as a DSO. yeah; separate thread on moving to core covers this particular issue
httpd -k start illegal option -- k
Current trunk gives the $ ./httpd -k start httpd: illegal option -- k $ ./httpd -V Server version: Apache/2.3.3-dev (Unix) Server built: Mar 28 2009 19:59:29 Server's Module Magic Number: 20090208:1 Server loaded: APR 2.0.0-dev, APR-UTIL 2.0.0-dev Compiled using: APR 2.0.0-dev, APR-UTIL 2.0.0-dev Architecture: 32-bit Server MPM: event threaded: yes (fixed thread count) forked: yes (variable process count) Server compiled with -D APACHE_MPM_DIR=server/mpm/event -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D DYNAMIC_MODULE_LIMIT=128 ... Is there some new config directive that needs to be added since mpm redesign, or it's just a temporary bug? Regards -- ^(TM)
Re: httpd -k start illegal option -- k
On 03/28/2009 08:11 PM, Mladen Turk wrote: Current trunk gives the $ ./httpd -k start httpd: illegal option -- k $ ./httpd -V Server version: Apache/2.3.3-dev (Unix) Server built: Mar 28 2009 19:59:29 Server's Module Magic Number: 20090208:1 Server loaded: APR 2.0.0-dev, APR-UTIL 2.0.0-dev Compiled using: APR 2.0.0-dev, APR-UTIL 2.0.0-dev Architecture: 32-bit Server MPM: event threaded: yes (fixed thread count) forked: yes (variable process count) Server compiled with -D APACHE_MPM_DIR=server/mpm/event -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D DYNAMIC_MODULE_LIMIT=128 ... Is there some new config directive that needs to be added since mpm redesign, or it's just a temporary bug? I guess it is bug that has something to do with how ap_mpm_rewrite_args is now called. Are you running on the latest trunk revision? Furthermore it was discovered that in conjunction with APR 2.0. it can lead to weird errors if you do not start from a fresh checkout but only update your working copy. Some old files are left then that are not caught by make clean / make extraclean. Please try again with latest trunk revision of httpd and APR and a fresh checkout of both. Regards RĂ¼diger