Re: Issues for 2.1.8
William A. Rowe, Jr. escreveu: Graham Leggett wrote: William A. Rowe, Jr. wrote: I don't mind rolling dice that the code is 'good enough' if it gets the votes here on list. Seriously, no objections. But it's too damned easy to get +1 ya, that's a cool new module, but I doubt it works, so throw it in experimental. Code that, anywhere else in the ASF, would never get the votes for release. And -that- is why experimental must die :) The trouble with new modules is that no matter how meticulously you went over it, there is always one platform that doesn't work (in the case of LDAP, the PITA platform was Windows), but if you don't release the code in case it might not work, it will never reach the people who have the resources to make it work. Yet - it's not experimental (taking the LDAP example). So we, as an entire group, agree to figure out how to build the danged thing so it's working on all platforms by the end of beta (and it was, in 2.0 working on all platforms, this has to do with the apr-util refactoring today, and it will work in 2.2 before we christen it GA.) I find it interesting that you choose to inflict the code on those with the resources to make it work. Does that mean, until it's been dropped (ignorantly) into production on high-end machines by less-cautious admins, that we don't expect to find out if it works or not? What *IS* experimental ... that is what I'm asking. LDAP in 2.2 isn't. Cache isn't any longer. mod_dbd or mod_filter? I dunno - haven't spent time there, but seriously why ship code that doesn't work, let's ship code that works and fix the bugs as they arrive. Support it or do not, that's fine, but once supported let's put our collective energies behind it. There is a natural threshold of effort above which people are far less likely to take the time out to help. An svn update is easy. Checking out and building an entirely separate sandbox is above the threshold for most people. I seriously -don't- expect the casual user to grab from svn. That's what svn snapshots, are for, that they can easily extract themselves. And this is why I suggested we seriously consider a CPAN-like proposal by sctemme ... and nobody seemed to grok this... ..HE DOES NOT PROPOSE A F'ING LIST OF MODULES... ...a cpan like facility is an entire mechasim for obtaining and dropping into your build all of the other modules that interest you. Trivial, no extra knowledge of what packages to download, which URL's to use. Yes, search.cpan.org is interesting, but if you thought that was what I had suggested, e.g. modules.apache.org, you missed it entirely. Witness the proxy changes to v2.0 in the proxyreq branch. The nature of the changes meant that a branch was 100% necessary, but the side effect was that it took far longer to review the changes than other code in the server. It amounted to a significant deviation from normal development patterns to test it properly, and so reduced the audience significantly. Ack. I would have voted for the original proxy to be re-added (and in fact, if you look back, odds on, I did.) Hindsite is a funny thing :) I would have probably voted for 2.0.39, not 2.0.35, to be GA ;-) And, although I've hinted that mod_proxy was sub-release quality, it was in fact released in modules/proxy/. Yes, parts had to be rewritten from scratch. You are probably a victim of my ire over mod_rewrite, of who's rewrite caused even more pain and constranation, and both modules were sufficiently complex to expect bugs from a major effort. Yes - cache was a *supported* 1.3 feature. We axed it, while stating that This version is the best available flavor of Apache http Server or something close to it. So sure, folks EXPECTED it to do what 1.3 did, including caching. And should they not have? This is why experimental must live. :) Ok... rereading... rereading... rereading... Still not seeing how your post justifies modules/experimental/... could you explain it again in a different way? Only Kevin has produced an interesting argument that I'm honestly quite drawn to, and JimJ has played on the concept in his posts. But on the whole, you haven't justified putting trash (well, it almost works) into modules/experimental/, as opposed to putting finished code (hmmm... this might not solve everyone's problems, but it's solid and it works) into a proper modules/FOO/ directory that corresponds to the function of that module. Bill William Bill Hitcock A. Rowe, hates stable apache releases? Please vote. P.S: From a new, new, very new timer
Rev: 2.1.7 Available for Testing Voting
On FreeBSD 4.10 GCC 2.95.4 Httpd 2.1.7-beta with -DDEBUG -DAPR_POOL_DEBUG occurs: In file included from pcre.c:543: printint.c: In function `get_ucpname': printint.c:118: `utt' undeclared (first use in this function) printint.c:118: (Each undeclared identifier is reported only once printint.c:118: for each function it appears in.) printint.c:118: `ucp_type_table' undeclared (first use in this function) printint.c:123: warning: control reaches end of non-void function *** Error code 1 Stop in /usr/src/httpd-2.1.7-beta/srclib/pcre. *** Error code 1 Stop in /usr/src/httpd-2.1.7-beta/srclib/pcre. *** Error code 1 Stop in /usr/src/httpd-2.1.7-beta/srclib. *** Error code 1 Stop in /usr/src/httpd-2.1.7-beta.
Re: Rev: 2.1.7 Available for Testing Voting
Sander Temme wrote: I'm running with this patch, with -DDEBUG, on FreeBSD 4.10 (and Darwin): http://marc.theaimsgroup.com/?l=apache-httpd-devm=111435689526926w=2 S. Thank you! Patch works!
Re: Compiling Apache 2.0.49 with worker MPM
Kotla, Satya (Corporate, consultant) wrote: But somehow after the compilation, I am seeing that it has included the prefork MPM instead of worker I Weel, I suppose that your system is FreeBSD? Because problems with libs (threads), doens't possible compilation multithread in FreeBSD with http (apr like). Please, see post http://groups.yahoo.com/group/new-httpd/message/47705 and your subsequentes posts. have ecen tried using --with-mpm=perchild option, but even then after compilation I am seeing only prefork.c in the list of modules included after compilation. Is there something wrong with configure script for Apache 2.0.49? Has anybody else faced this problem? FreeBSD 5.X, apparently solved the problem...
Re: Help in Writing Apache Modules in C
Nick Kew wrote: On Wed, 28 Jan 2004, Will Lowe wrote: If you're looking for Apache 1.x (not 2.x) Given that he's writing C, and that 2.x is a vastly richer development environment than 1.3, why should he even consider that? In 1.3 days, application developers had to resort to all kinds of add-ons, none of which are in C. If it had had the power of the 2.0 API, we'd probably still have CGI and PHP at the bottom end, of add-ons, but the need for backends like Tomcat would probably never have been felt. Awaiting for a Helping Hand. Suggest looking at existing modules, and reading the nicely-documented Apache header files. Look at http://modules.apache.org/doc/Intro_API_Prog.html and http://www.oreillynet.com/pub/ct/38 and http://threebit.net/tutorials/apache2_modules/tut1/tutorial1.html Ranier.
Possible security flaw! (Format BUG)
Hello All, I tested the source code of httpd-2.0.47, with tool pscan (format bug scanner) and possible security flaws is found! Please, anybody can check if this is real problem of security? Thanks. Ranier Vilela RC Software Ltda. [EMAIL PROTECTED] pscan]# ./pscan -vv -w -p wu-ftpd.pscan /usr/src/httpd-2.0.47/server/*.c Scanning /usr/src/httpd-2.0.47/server/buildmark.c ... Scanning /usr/src/httpd-2.0.47/server/config.c ... /usr/src/httpd-2.0.47/server/config.c:434 FUNC printf format string with 1 parameters: OK /usr/src/httpd-2.0.47/server/config.c:1485 FUNC fprintf format string with 2 parameters: OK /usr/src/httpd-2.0.47/server/config.c:1491 FUNC fprintf format string with 2 parameters: OK /usr/src/httpd-2.0.47/server/config.c:1497 FUNC fprintf format string with 2 parameters: OK /usr/src/httpd-2.0.47/server/config.c:1511 FUNC fprintf format string with 3 parameters: OK /usr/src/httpd-2.0.47/server/config.c:1894 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1898 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1901 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1904 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1911 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1914 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1917 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1920 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1924 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1926 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1931 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1933 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1938 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1940 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1945 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1947 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1952 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1954 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1959 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1973 FUNC printf format string with 2 parameters: OK /usr/src/httpd-2.0.47/server/config.c:1976 FUNC printf format string with 1 parameters: OK /usr/src/httpd-2.0.47/server/config.c:1988 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/config.c:1990 FUNC printf format string with 1 parameters: OK Scanning /usr/src/httpd-2.0.47/server/connection.c ... Scanning /usr/src/httpd-2.0.47/server/core.c ... Scanning /usr/src/httpd-2.0.47/server/error_bucket.c ... Scanning /usr/src/httpd-2.0.47/server/exports.c ... Scanning /usr/src/httpd-2.0.47/server/gen_test_char.c ... /usr/src/httpd-2.0.47/server/gen_test_char.c:83 FUNC printf format string with 5 parameters: OK /usr/src/httpd-2.0.47/server/gen_test_char.c:105 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/gen_test_char.c:150 FUNC printf format string with 2 parameters: OK /usr/src/httpd-2.0.47/server/gen_test_char.c:153 FUNC printf Last argument is variable or reference: BAD Scanning /usr/src/httpd-2.0.47/server/listen.c ... Scanning /usr/src/httpd-2.0.47/server/log.c ... /usr/src/httpd-2.0.47/server/log.c:559 FUNC syslog format string with 1 parameters: OK Scanning /usr/src/httpd-2.0.47/server/main.c ... /usr/src/httpd-2.0.47/server/main.c:91 FUNC printf format string with 1 parameters: OK /usr/src/httpd-2.0.47/server/main.c:92 FUNC printf format string with 1 parameters: OK /usr/src/httpd-2.0.47/server/main.c:93 FUNC printf format string with 2 parameters: OK /usr/src/httpd-2.0.47/server/main.c:101 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/main.c:103 FUNC printf format string with 1 parameters: OK /usr/src/httpd-2.0.47/server/main.c:107 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/main.c:111 FUNC printf format string with 1 parameters: OK /usr/src/httpd-2.0.47/server/main.c:115 FUNC printf Last argument is variable or reference: BAD /usr/src/httpd-2.0.47/server/main.c
Re: kqueue a alternative poll/select?
Bill wrote: The apr_pollset API in APR would be a suitable wrapper for a kqueue or dev/poll implementation, but no one has spent the time and effort to do it yet. I have a prototype httpd implementation (patch posted to this list months ago) that implements event driven network reads and Ian Holsman wrote up a design for doing event driven writes. That's about it. Thanks for your reply, I would like to help more. However, still I do not have capacity to contribute with complex codes. I have hopes to improve. Thanks. Ranier.
kqueue a poll/select alternative?
Hi, Anyone knows about kqueue, dev/poll implementation in apr, httpd? Thanks. Ranier.
kqueue a alternative poll/select?
Hi, Anyone knows about implementation of kqueue, dev/poll in apr, httpd? Thanks. Ranier
[PACTH] sdbm.c, silent warning messages on gcc 2.95.3 with debug
--- sdbm-old.c 2003-07-08 19:55:04.0 -0300 +++ sdbm.c 2003-07-08 19:57:52.0 -0300 @@ -495,7 +495,7 @@ while (dbit db-maxbno getdbit(db, dbit)) dbit = 2 * dbit + ((hash (1 hbit++)) ? 2 : 1); -debug((dbit: %d..., dbit)); +debug((dbit: %lu..., dbit)); db-curbit = dbit; db-hmask = masks[hbit]; @@ -520,7 +520,7 @@ return APR_ENOSPC; /* ### better error? */ db-pagbno = pagb; -debug((pag read: %d\n, pagb)); +debug((pag read: %lu\n, pagb)); } return APR_SUCCESS; } @@ -540,7 +540,7 @@ db-dirbno = dirb; -debug((dir read: %d\n, dirb)); +debug((dir read: %lu\n, dirb)); } return db-dirbuf[c % DBLKSIZ] (1 dbit % BYTESIZ); @@ -563,7 +563,7 @@ db-dirbno = dirb; -debug((dir read: %d\n, dirb)); +debug((dir read: %lu\n, dirb)); } db-dirbuf[c % DBLKSIZ] |= (1 dbit % BYTESIZ);
