Module reports busy workers
Hi, I would like to implement a module that write information (busy worker and idle worker) in file. When request is processed, It writes information (ap_log_hook). I use mod_status to recovery these information. I don't know about use these information in my module. Ricardo -- View this message in context: http://www.nabble.com/Module-reports-busy-workers-tp25151145p25151145.html Sent from the Apache HTTP Server - Module Writers mailing list archive at Nabble.com.
Re: Module reports busy workers
On Wed, Aug 26, 2009 at 8:47 AM, ricardo13ricardoogra...@gmail.com wrote: Hi, I would like to implement a module that write information (busy worker and idle worker) in file. When request is processed, It writes information (ap_log_hook). I use mod_status to recovery these information. I don't know about use these information in my module. mod_status is less than a thousand lines of code and already has all of this logic. What part of mod_status are you having trouble understanding, specifically? -- Eric Covener cove...@gmail.com
Re: Module reports busy workers
HI, How do I collect these informations in my module ? Ricardo ricardo13 wrote: Hi, I would like to implement a module that write information (busy worker and idle worker) in file. When request is processed, It writes information (ap_log_hook). I use mod_status to recovery these information. I don't know about use these information in my module. Ricardo -- View this message in context: http://www.nabble.com/Module-reports-busy-workers-tp25151145p25151432.html Sent from the Apache HTTP Server - Module Writers mailing list archive at Nabble.com.
Re: Module reports busy workers
On Wed, Aug 26, 2009 at 11:56 AM, ricardo13ricardoogra...@gmail.com wrote: HI, How do I collect these informations in my module ? Same way mod_status does? -- Eric Covener cove...@gmail.com
Re: Module reports busy workers
Yes, Mod_status shows in browser and writes in file. But mod_status writes in a file only when I stop apache. Ricardo Eric Covener wrote: On Wed, Aug 26, 2009 at 11:56 AM, ricardo13ricardoogra...@gmail.com wrote: HI, How do I collect these informations in my module ? Same way mod_status does? -- Eric Covener cove...@gmail.com -- View this message in context: http://www.nabble.com/Module-reports-busy-workers-tp25151145p25156808.html Sent from the Apache HTTP Server - Module Writers mailing list archive at Nabble.com.
Re: Analysis of the Apache web server code repository
Hi Jeff, thanks for taking the time to take a look! Jeff Trawick wrote: It is fun to be in the movies; maybe I'll make my kids sit through it later ;) (And I'm curious which company you found when you looked up trawick.) First link on google: http://www.trawick.com/, Mastering enterprise IT challenges with integrity But please note that ASF ids aren't shared. It is important for the integrity of the code that we know who is making contributions. You should remove the overlaid text that suggests that any ASF work is being done by a commercial entity using shared ids. ...ups? Sorry about that, the corrected video is now available on-line. When I saw the time profile of the changes and also saw a web site of a company called Trawick mentioning things like cost-effective IT solutions, I guess I saw what I wanted to see. Just so you know, I substituted: Looked it up. It seems it is a company. :) with Looked it up. I was _sure_ it is a company...but was corrected by the Apache devs when they saw the video - it's a person. Careful how you interpret the data! :) (All I can say about when I commit historically is that I like to sleep at least from midnight to six a.m. US Eastern Time, at least when I'm at home ;) I don't think the same is true of many other people (wrowe).) :) Cheers, Tomislav -- http://www.PanBI.org - business intelligence everywhere!
Re: Analysis of the Apache web server code repository
Bill Stoddard wrote: Tomislav, This is a very interesting and clever tool, but you probably just stepped on some toes around here, perhaps without realizing it. If you know anything about ASF culture, you know that we don't participate in projects as 'company representatives'. We participate as individuals and as Jeff points out, user id's are not shared. Agree w/Jeff that you should remove the text in the overlay that suggests otherwise. Bill, thank you for the correction: I definitely did not want to step on anyones toes and didn't think too much of it. As I had already told Jeff, I read too much into what I saw so I didn't bother to check it further. I hope the new label will help other eager analysts avoid committing a mistake or two of their own. :) The tool may be clever, but the tool builders...less flattering descriptions come to mind. ;) Cheers, Tomislav -- http://www.PanBI.org - business intelligence everywhere!
Re: Analysis of the Apache web server code repository
I knew Trawick was a slacker most of the time. Now there's cool pie charts and movies to prove it. ROFL Hmm... why do I get the feeling this tool's real usage is so that IT managers can see who they can 'let go'? Kevin Kiley -Original Message- From: Jeff Trawick traw...@gmail.com To: dev@httpd.apache.org Sent: Tue, Aug 25, 2009 4:26 pm Subject: Re: Analysis of the Apache web server code repository On Tue, Aug 25, 2009 at 3:45 PM, t.n.a. t...@sharanet.org wrote: I have designed a dedicated Subversion data warehouse and loading logic so that Subversion repository data can be analyzed using OLAP tools. To demonstrate the functionality, I have made a short screencast http://panbi.sourceforge.net/systems/subversion/olap.html (7 minutes) using none other than the Apache web server's code repository as the one under analysis. It is fun to be in the movies; maybe I'll make my kids sit through it later ;)? (And I'm curious which company you found when you looked up trawick.) But please note that ASF ids aren't shared.? It is important for the integrity of the code that we know who is making contributions.? You should remove the overlaid text that suggests that any ASF work is being done by a commercial entity using shared ids. (All I can say about when I commit historically is that I like to sleep at least from midnight to six a.m. US Eastern Time, at least when I'm at home ;)? I don't think the same is true of many other people (wrowe).) Thanks!
Fwd: How to configure mod_jk+loadbalance+https in Apache 2.2
-- Forwarded message -- From: run sir runsir...@gmail.com Date: Wed, Aug 26, 2009 at 11:14 AM Subject: How to configure mod_jk+loadbalance+https in Apache 2.2 To: us...@httpd.apache.org Hi, i am setting Apache https forward and loadbalance with mod_jk on tomcat, /etc/httpd/config/httpd.conf as below: SSLProxyEngine on LoadModule jk_module modules/mod_jk.so IfModule mod_jk.c JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel info JkLogStampFormat[%a %b %d %H:%M:%S %Y] JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories JkRequestLogFormat %w %V %T Location /*/WEB-INF/* AllowOverride None deny from all /Location Location /*/META-INF/* AllowOverride None deny from all /Location # forward ALL web requests to our mod_jk loadbalancer workers JkMount /servlet-examples-cluster/* loadbalancer /IfModule workers.properties worker.list=loadbalancer,status worker.maintain=60 #worker.NODE1.type=ajp13 #worker.NODE1.host=9.186.10.65 #worker.NODE1.port=8009 #worker.NODE1.socket_timeout=60 #worker.NODE1.socket_keepalive=true #worker.NODE1.lbfactor=1 #worker.NODE2.port=8009 #worker.NODE2.host=9.186.10.167 #worker.NODE2.type=ajp13 #worker.NODE2.socket_timeout=60 #worker.NODE2.socket_keepalive=true #worker.NODE2.lbfactor=1 worker.NODE3.host=9.186.10.65 worker.NODE3.type=ajp13 worker.NODE3.socket_timeout=60 worker.NODE3.socket_keepalive=true worker.NODE3.lbfactor=1 worker.NODE4.host=9.186.10.68 worker.NODE4.type=ajp13 worker.NODE4.socket_timeout=60 worker.NODE4.socket_keepalive=true worker.NODE4.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=NODE3,NODE4 worker.loadbalancer.sticky_session=true worker.status.type=status But it can't forward https request like https://localhost/servlet-examples-cluster/index.jsp to memebers of loadbalancer group, if i use mod_proxy , it works fine with above setting. Can somebody figure out what's wrong with my configuration about mod_jk, thanks a lot!
Re: Analysis of the Apache web server code repository
On Wed, Aug 26, 2009 at 2:02 AM, t.n.a. t...@sharanet.org wrote: Hi Jeff, thanks for taking the time to take a look! Jeff Trawick wrote: It is fun to be in the movies; maybe I'll make my kids sit through it later ;) (And I'm curious which company you found when you looked up trawick.) First link on google: http://www.trawick.com/, Mastering enterprise IT challenges with integrity That's not me, but it is good to know in case of corporate upheaval (long lost cousin perhaps?). Just so you know, I substituted: Looked it up. It seems it is a company. :) with Looked it up. I was _sure_ it is a company...but was corrected by the Apache devs when they saw the video - it's a person. Careful how you interpret the data! :) works for me Cheers, Tomislav Dobar dan -- Born in Roswell... married an alien...
Re: Scoreboard API
William A. Rowe, Jr. wrote: Well, the original question was more oriented to additional-data-per-slot. It should be fairly straightforward to allocate a shm to track children (for example, mod_fcgid does this) but it seemed silly to create a whole new shm for a handful of bytes per worker, when the data is worker oriented. The API would have a few issues; it becomes impossible to gracefully restart when adding the module; when removing the module the space must still be fixed at its initial allocation. If you want to create more workers, that sounds outside the scope of this initial thought, and more in line with mpm design, so your direction seems like an extention to the mpm logic (if they will be 'workers' with 'requests'). Thanks for your thoughts. The graceful restart issue is indeed one I have not thought through. As regards MPM logic, yes and no. Yes, that is certainly where I'm heading in terms of the 2.0/2.2 design. But I'm trying very hard to do that without writing a new MPM. I want to write a module that will be compatible with every MPM, and I'm looking to least- disruptive hooks in to what is currently MPM-private in order to be able to interact with MPM logic. OK, let's explain a bit more. The problem at hand is to be able to create child_init/drop_privileges functions that will act differently on different children: child1 -- normal child as we know it child2 -- special-purpose slave Once the configuration is determined, the module allocates a record of all special slaves in a (hypothetical) setup_scoreboard phase. Then the child_init hook checks the scoreboard for any vacant special-slave slots, and becomes the slave if there's a vacancy, noting its PID as occupying that slot. Having the record in scoreboard serves to keep track of the slave children over child_exits, and enables children to be treated unequally without having to hack it into the code of any (or every) existing MPM. Bit of modularity, like we have everywhere else! -- Nick Kew
Re: Analysis of the Apache web server code repository
toki...@aol.com wrote: I knew Trawick was a slacker most of the time. Now there's cool pie charts and movies to prove it. ROFL Hmm... why do I get the feeling this tool's real usage is so that IT managers can see who they can 'let go'? Kevin Kiley Uh oh... first I show on list up out of the blue, then you. What's next? Maybe stein and rbb show up and we can start a flame war on gzip compression? :-) Cheers, Bill
Re: Fwd: How to configure mod_jk+loadbalance+https in Apache 2.2
Hello, this is a list for the discussion of development topics concerning the Apache web server. The module mod_jk is developed as part of the Apache Tomcat project. Your questions about how to configure mod_jk should be posted to the discussion list us...@tomcat.apache.org Regards, Rainer On 26.08.2009 08:43, run sir wrote: -- Forwarded message -- From: *run sir* runsir.lu http://runsir.lu@gmail.com http://gmail.com Date: Wed, Aug 26, 2009 at 11:14 AM Subject: How to configure mod_jk+loadbalance+https in Apache 2.2 To: us...@httpd.apache.org mailto:us...@httpd.apache.org Hi, i am setting Apache https forward and loadbalance with mod_jk on tomcat, /etc/httpd/config/httpd.conf as below: SSLProxyEngine on LoadModule jk_module modules/mod_jk.so IfModule mod_jk.c JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel info JkLogStampFormat[%a %b %d %H:%M:%S %Y] JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories JkRequestLogFormat %w %V %T Location /*/WEB-INF/* AllowOverride None deny from all /Location Location /*/META-INF/* AllowOverride None deny from all /Location # forward ALL web requests to our mod_jk loadbalancer workers JkMount /servlet-examples-cluster/* loadbalancer /IfModule workers.properties worker.list=loadbalancer,status worker.maintain=60 #worker.NODE1.type=ajp13 #worker.NODE1.host=9.186.10.65 #worker.NODE1.port=8009 #worker.NODE1.socket_timeout=60 #worker.NODE1.socket_keepalive=true #worker.NODE1.lbfactor=1 #worker.NODE2.port=8009 #worker.NODE2.host=9.186.10.167 #worker.NODE2.type=ajp13 #worker.NODE2.socket_timeout=60 #worker.NODE2.socket_keepalive=true #worker.NODE2.lbfactor=1 worker.NODE3.host=9.186.10.65 worker.NODE3.type=ajp13 worker.NODE3.socket_timeout=60 worker.NODE3.socket_keepalive=true worker.NODE3.lbfactor=1 worker.NODE4.host=9.186.10.68 worker.NODE4.type=ajp13 worker.NODE4.socket_timeout=60 worker.NODE4.socket_keepalive=true worker.NODE4.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=NODE3,NODE4 worker.loadbalancer.sticky_session=true worker.status.type=status But it can't forward https request like https://localhost/servlet-examples-cluster/index.jsp to memebers of loadbalancer group, if i use mod_proxy , it works fine with above setting. Can somebody figure out what's wrong with my configuration about mod_jk, thanks a lot!
Re: svn commit: r807823 - /httpd/mod_fcgid/trunk/CHANGES-FCGID
On Wed, Aug 26, 2009 at 1:10 AM, William A. Rowe, Jr. wr...@rowe-clan.netwrote: Chris Darroch wrote: wr...@apache.org wrote: URL: http://svn.apache.org/viewvc?rev=807823view=rev Log: suppose this would be worth noting Changes with mod_fcgid 2.3.1 + *) Complete the unix port to 2.3-dev trunk. [William Rowe] Thank you for all this work ... it's much appreciated, especially since I've been utterly useless lately on the httpd front. Thanks again! So... if I throw the effort at getting unix to build clean for httpd-2.0 branch, you won't be offended ;-? (brain dump since I have to get some real work done) Here's a patch to get the proper header files included for the apr 0.9.x compatibility code. http://people.apache.org/~trawick/fcgid_2.0.x_detect.patch Is it worth the trouble to make that ugly code (copy of apr_shm_remove) compile correctly? Should we just add that function to the not-anally-versioned APR 0.9.x? My configure.apxs build currently fails to find mod_fcgid.a; that doesn't seem to be related to the patch, but that knowledge brings only so much happiness... And I haven't tried building in-tree.
Re: four potential bugs discovered from CWRU research group
Has anyone looked at these bugs yet? I would really appreciate it if
someone can comment on the bugs.
On Sat, Aug 22, 2009 at 12:04 PM, Boya Sun bxs...@case.edu wrote:
Dear Apache-httpd programmers:
This is Boya Sun from Case Western Reserve University. I have sent you
some potential bugs we discovered in our recent research a few days ago, but
I haven’t got any response yet, so I tried to organize the bugs and
resubmitted these 4 potential bugs. I rewrite the potential bugs and the
potential fixes in the form of patches. Most of the patches are against the
trunk (revision 806655), except for the second one, which is against the
branch of 2.2.x at revision 806782. The patch for BUG2 is not a real bug
fix, but just some comments indicating where the missing code should be
added, since I am not exactly sure how to fix the bug.
I STRONGLY RECOMMEND you to go over these potential bugs, since these
potential bugs are very similar to some previous bugs in your issue DB or
some revisions that looks like bug-fix, which provide strong evidence that
these potential bugs are real ones.
In order to make it easier to understand, for each bug we discovered, I
also show the original bug-fix which we used to discover the new bugs.
I would REALLY appreciate that you could help us confirm whether these
bug-fixes are valid or not, since this is the ONLY way for us to know
whether our approach of discovering new bugs works.
Thanks very much in advance! And enjoy viewing the bugs……:-)
BUG1:
Description: This bug was found by analyzing bug 31440 (
https://issues.apache.org/bugzilla/show_bug.cgi?id=31440); this fix
replaced srand((int) time((time_t *) NULL)) function with seed_rand() in
order to improve rand seed generation under the cases ALG_APMD5 and
ALG_CRYPT.
We have found that in the file htdbm.c, there are code segments that are
very similar to the bug being fixed in 31440. We believe that in this file,
srand((int) time((time_t *) NULL)) should also be replaced with
seed_rand() for cases ALG_APMD5 and ALG_CRYPT
**original
bug-fix*
--- htpasswd.c (revision 629163)
+++ htpasswd.c (revision 629164)
@@ -126,6 +126,18 @@
}
}
+static apr_status_t seed_rand()
+{
+int seed = 0;
+apr_status_t rv;
+rv = apr_generate_random_bytes((unsigned char*) seed, sizeof(seed));
+if (rv) {
+apr_file_printf(errfile, Unable to generate random bytes: %pm
NL, rv);
+return rv;
+}
+srand(seed);
+return rv;
+}
static void putline(apr_file_t *f, const char *l)
{
@@ -174,7 +186,9 @@
break;
case ALG_APMD5:
-(void) srand((int) time((time_t *) NULL));
+if (seed_rand()) {
+break;
+}
generate_salt(salt[0], 8);
salt[8] = '\0';
@@ -190,7 +204,9 @@
#if (!(defined(WIN32) || defined(TPF) || defined(NETWARE)))
case ALG_CRYPT:
default:
-(void) srand((int) time((time_t *) NULL));
+if (seed_rand()) {
+break;
+}
to64(salt[0], rand(), 8);
salt[8] = '\0';
*discovered potential bug and possible
fix*
--- support/htdbm.c (revision 806655)
+++ support/htdbm.c (working copy)
@@ -298,7 +298,9 @@
break;
case ALG_APMD5:
-(void) srand((int) time((time_t *) NULL));
+if (seed_rand()) {
+break;
+ }
to64(salt[0], rand(), 8);
salt[8] = '\0';
apr_md5_encode((const char *)htdbm-userpass, (const char
*)salt,
@@ -314,7 +316,9 @@
break;
#if (!(defined(WIN32) || defined(NETWARE)))
case ALG_CRYPT:
-(void) srand((int) time((time_t *) NULL));
+if (seed_rand()) {
+break;
+ }
to64(salt[0], rand(), 8);
salt[8] = '\0';
apr_cpystrn(cpw, crypt(htdbm-userpass, salt), sizeof(cpw) -
1);
BUG2:
Description: This bug was found by analyzing revision 602467 (
http://svn.apache.org/viewvc?view=revrevision=602467)
The log of this revision is as follows:
* core log.c: Work around possible solutions rejected by apr for the old
implementation of apr_proc_create(), and explicitly pass the output and
error channels to all log processes created. This goes all the way back to
piped logs failing to run on win32. Not in or needed at trunk/, as apr 1.3.0
has the proper fix.
Note that this bug seems to be particular to the 2.2.x branch, so the ewe
searched for similar bugs in
https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x at revision
806782 , instead ot the trunk.
From the above bug-fix, it seems that before calling apr_proc_create,
apr_procattr_child_out_set and apr_procattr_child_err_set should be
invoked on procattr; however, we have found a bug that these two functions
Re: four potential bugs discovered from CWRU research group
Boya Sun wrote: Has anyone looked at these bugs yet? I would really appreciate it if someone can comment on the bugs. Have you entered them in Bugzilla at issues.apache.org? They seem to reference existing bug reports there, so a comment on those might be in order. What you posted to the list is rather hard to read, because your mailer has formatted it as pseudo-HTML. -- Nick Kew
Re: four potential bugs discovered from CWRU research group
Thanks very much for your reply, Nick! I am still new to this list and bugzilla, so is it OK that I comment on resolved bugs which has been fixed two years ago? If so, I will do that and post comments on the bugs I referenced. Thanks very much again! Boya On Wed, Aug 26, 2009 at 11:19 AM, Nick Kew n...@webthing.com wrote: Boya Sun wrote: Has anyone looked at these bugs yet? I would really appreciate it if someone can comment on the bugs. Have you entered them in Bugzilla at issues.apache.org? They seem to reference existing bug reports there, so a comment on those might be in order. What you posted to the list is rather hard to read, because your mailer has formatted it as pseudo-HTML. -- Nick Kew -- BOYA SUN Computer Science Division Electrical Engineering Computer Science Department 513 Olin Building Case Western Reserve University 10900 Euclid Avenue Cleveland, OH 44106 boya@case.edu
Re: svn commit: r807823 - /httpd/mod_fcgid/trunk/CHANGES-FCGID
Jeff Trawick wrote: (brain dump since I have to get some real work done) :) Here's a patch to get the proper header files included for the apr 0.9.x compatibility code. http://people.apache.org/~trawick/fcgid_2.0.x_detect.patch Is it worth the trouble to make that ugly code (copy of apr_shm_remove) compile correctly? Should we just add that function to the not-anally-versioned APR 0.9.x? Sure. Let's get it building correctly without updating 0.9.x; it serves as a good example of this module build schema. The four lines of fchmod example in configure.apxs be deleted. And it appears there is a stray ')' at the end of your revised APACHE_MODULE line. Just need to strip all these checks when brought into httpd trunk, if we do so. My configure.apxs build currently fails to find mod_fcgid.a; that doesn't seem to be related to the patch, but that knowledge brings only so much happiness... And I haven't tried building in-tree. :) How does modules.mk from .apxs compare with a normal modules.mk that would exist in one of your modules/ subdirectories of a normal 2.0 build? Is it invoking the right libtool (copied into apr/build/)? There are some flaws in the httpd-2.0 installation still, particularly if apr ends up installed in a different directory than httpd.
Re: svn commit: r807823 - /httpd/mod_fcgid/trunk/CHANGES-FCGID
William A. Rowe, Jr. wrote: Jeff Trawick wrote: (brain dump since I have to get some real work done) :) Here's a patch to get the proper header files included for the apr 0.9.x compatibility code. And if I wasn't clear, please feel free to dump this into svn, I'll assure it doesn't break anything before I tag and roll. We gotta keep your stats up in Tomislav's analysis :) Bill
Re: svn commit: r807823 - /httpd/mod_fcgid/trunk/CHANGES-FCGID
William A. Rowe, Jr. wrote: Thank you for all this work ... it's much appreciated, especially since I've been utterly useless lately on the httpd front. Thanks again! So... if I throw the effort at getting unix to build clean for httpd-2.0 branch, you won't be offended ;-? Seriously, no troubles, I'd just like to see this released, so we get bug reports, so that we fix them, so that this becomes more relevant and ends up in the 2.3-dev tree :) Absolutely, and again, apologies for being a useless lump at the moment. I'm rolling sometime tomorrow. If folks can check out, test compile and experiment, I'd be most appreciative. It would be lovely if it could go GA on the first try. I can't make a promise but I'll try to grab it and spin it up. Again, thank you. Chris. -- GPG Key ID: 366A375B GPG Key Fingerprint: 485E 5041 17E1 E2BB C263 E4DE C8E3 FA36 366A 375B
Re: svn commit: r807823 - /httpd/mod_fcgid/trunk/CHANGES-FCGID
On Wed, Aug 26, 2009 at 12:56 PM, William A. Rowe, Jr. wr...@rowe-clan.netwrote: William A. Rowe, Jr. wrote: Jeff Trawick wrote: (brain dump since I have to get some real work done) :) Here's a patch to get the proper header files included for the apr 0.9.x compatibility code. And if I wasn't clear, please feel free to dump this into svn, I'll assure it doesn't break anything before I tag and roll. Yep (I'll take a few minutes to fix/test further based on your comments.) We gotta keep your stats up in Tomislav's analysis :) Yes, André is breathing down my neck.
Re: Analysis of the Apache web server code repository
Ah... the good 'ol days. -Original Message- From: Bill Stoddard wgstodd...@gmail.com To: dev@httpd.apache.org Sent: Wed, 26 Aug 2009 06:45:11 -0400 Subject: Re: Analysis of the Apache web server code repository toki...@aol.com wrote: I knew Trawick was a slacker most of the time. Now there's cool pie charts and movies to prove it. ROFL Hmm... why do I get the feeling this tool's real usage is so that IT managers can see who they can 'let go'? Kevin Kiley Uh oh... first I show on list up out of the blue, then you. What's next? Maybe stein and rbb show up and we can start a flame war on gzip compression? :-) Cheers, Bill
Re: Analysis of the Apache web server code repository
Ah... the good 'ol days. -Original Message- From: Bill Stoddard wgstodd...@gmail.com To: dev@httpd.apache.org Sent: Wed, 26 Aug 2009 06:45:11 -0400 Subject: Re: Analysis of the Apache web server code repository toki...@aol.com wrote: I knew Trawick was a slacker most of the time. Now there's cool pie charts and movies to prove it. ROFL Hmm... why do I get the feeling this tool's real usage is so that IT managers can see who they can 'let go'? Kevin Kiley Uh oh... first I show on list up out of the blue, then you. What's next? Maybe stein and rbb show up and we can start a flame war on gzip compression? :-) Cheers, Bill
Re: svn commit: r807823 - /httpd/mod_fcgid/trunk/CHANGES-FCGID
Hi Bill and Chris, Question, is this going to work with APR 1.3 on Windows? I see this http://svn.apache.org/viewvc?view=revrevision=787561 but when I look at what I was given by Tom Donovan he seemed to have to deal with APR 1.3 as a #if seperate entity #endif, nasty yes but it works. My build out-of-tree on the 19th builds and loads fine but when it is called upon it did this; Faulting application httpd.exe, version 2.2.13.0, faulting module libapr-1.dll, version 1.3.8.0, fault address 0x793d. This failure in libapr-1.dll leave me a bit suspicious. My usual disclaimer, I will not deny this may possibly be my fault. Regards, Gregg William A. Rowe, Jr. wrote: Chris Darroch wrote: wr...@apache.org wrote: URL: http://svn.apache.org/viewvc?rev=807823view=rev Log: suppose this would be worth noting Changes with mod_fcgid 2.3.1 I'm rolling sometime tomorrow. If folks can check out, test compile and experiment, I'd be most appreciative. It would be lovely if it could go GA on the first try.
Re: svn commit: r807823 - /httpd/mod_fcgid/trunk/CHANGES-FCGID
Gregg L. Smith wrote: Faulting application httpd.exe, version 2.2.13.0, faulting module libapr-1.dll, version 1.3.8.0, fault address 0x793d. Gregg, your Dr Watson or windbg fault backtrace please?
Re: svn commit: r797647 - /httpd/mod_fcgid/trunk/mod_fcgid/mod_fcgid.c
On Fri, Jul 24, 2009 at 4:54 PM, wr...@apache.org wrote: Author: wrowe Date: Fri Jul 24 20:54:46 2009 New Revision: 797647 URL: http://svn.apache.org/viewvc?rev=797647view=rev Log: use our apr specific methods of merging this server config table and array Modified: httpd/mod_fcgid/trunk/mod_fcgid/mod_fcgid.c Modified: httpd/mod_fcgid/trunk/mod_fcgid/mod_fcgid.c URL: http://svn.apache.org/viewvc/httpd/mod_fcgid/trunk/mod_fcgid/mod_fcgid.c?rev=797647r1=797646r2=797647view=diff == --- httpd/mod_fcgid/trunk/mod_fcgid/mod_fcgid.c (original) +++ httpd/mod_fcgid/trunk/mod_fcgid/mod_fcgid.c Fri Jul 24 20:54:46 2009 @@ -99,6 +100,71 @@ return APR_SUCCESS; } + +/* This should be proposed as a stand-alone improvement to the httpd module, + * either in the arch/ platform-specific modules or util_script.c from whence + * it came. + */ +static void default_proc_env(apr_table_t *e) do you have any code yet to call this function?
Re: mod_cache, mod_deflate and Vary: User-Agent
On Wed, Aug 26, 2009 at 11:47 AM, William A. Rowe, Jr.wr...@rowe-clan.net wrote: I think we blew it :) Vary: user-agent is not practical for correcting errant browser behavior. For example; User-Agent: Mozilla/5.0 Gecko/20090729 Firefox/3.5.2 produces a myriad number of 'variant' flavors when tagging Vary with the User-Agent when determining if the deflate/gzip compression should be served, or the uncompressed variant. What we really meant to do was to determine which Accept-Encoding values were invalid based on known browser bugs, and -remove them- from the A-E header *prior* to determining the cache handling (quick handler hook) or typical content handling. Which implies that setenvif + headers need an extra chance to run really first in front of the quick handler. Any better suggestions? Yes, write a Varied header to 'hash' plugin API for mod_cache. I would write little lua scriptlets that map user agents to two buckets: supports gzip, doesnt support gzip. store the thing in mod_cache only twice, instead of once for every user agent.
Re: svn commit: r807823 - /httpd/mod_fcgid/trunk/CHANGES-FCGID
Hi Bill, Since I had tossed it all you forced me to rebuild. I do not remember doing anything different prior but The Culprit; My usual disclaimer, I will not deny this may possibly be my fault. Sorry and Thanks for getting this module going. I can think of a lot of people that will be very happy now that the ASF has taken it over. Gregg William A. Rowe, Jr. wrote: Gregg L. Smith wrote: Faulting application httpd.exe, version 2.2.13.0, faulting module libapr-1.dll, version 1.3.8.0, fault address 0x793d. Gregg, your Dr Watson or windbg fault backtrace please? No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.69/2328 - Release Date: 08/26/09 12:16:00
Re: Analysis of the Apache web server code repository
toki...@aol.com wrote: I knew Trawick was a slacker most of the time. Now there's cool pie charts and movies to prove it. ROFL I _knew_ my mail would get a lively response on this list! ;-) Hmm... why do I get the feeling this tool's real usage is so that IT managers can see who they can 'let go'? Hi Kevin, my brother (also a software engineer) basically said the same thing. Personally, I've ran into the exact opposite case: a company I know has trouble deciding who to give bonuses to as it's getting harder and harder to estimate developers' contributions. To this company, this kind of insight, while not perfect by a long shot, is very valuable - so that they can reward people. Oh, and wait till you see time tracker analysis: http://panbi.sourceforge.net/systems/worktime/olap.html ;) Cheers, Tomislav -- http://www.PanBI.org - business intelligence everywhere!
Re: mod_cache, mod_deflate and Vary: User-Agent
Paul Querna wrote: Yes, write a Varied header to 'hash' plugin API for mod_cache. I would write little lua scriptlets that map user agents to two buckets: supports gzip, doesnt support gzip. store the thing in mod_cache only twice, instead of once for every user agent. This doesn't solve the problem of each-and-every downstream proxy cache storing an excessively large number of copies. Even if we strip down comments from the fields before choosing cache entries, Mozilla's many versions of Mozilla/2.0.3 and Gecko/20090731 tags are going to continue to proliferate copies. I'm suggesting that this might need to be 'invisibly' handled, not using Vary:, but by any proxy clever enough to detect the non-conforming browser to then strip the request to deflate/gzip. At that point, the choice-of-two becomes obvious to all proxies and back end servers with this knowledge. If this is unknown to an earlier proxy, the client could get the broken deflate/gzip content, but that seems unavoidable. Honestly, I can't see a way to honor HTTP/1.1 cache negotiation goals while minimizing cache pollution. I did consider a module (lua or otherwise) that would 'interfere' in the initial quick handler phase just to work out broken user agents, rather than carry the entire weight of setenvif/headers to the quick handler phase.
Re: mod_cache, mod_deflate and Vary: User-Agent
On Wed, Aug 26, 2009 at 2:50 PM, William A. Rowe, Jr.wr...@rowe-clan.net wrote: Paul Querna wrote: Yes, write a Varied header to 'hash' plugin API for mod_cache. I would write little lua scriptlets that map user agents to two buckets: supports gzip, doesnt support gzip. store the thing in mod_cache only twice, instead of once for every user agent. This doesn't solve the problem of each-and-every downstream proxy cache storing an excessively large number of copies. Even if we strip down comments from the fields before choosing cache entries, Mozilla's many versions of Mozilla/2.0.3 and Gecko/20090731 tags are going to continue to proliferate copies. I'm suggesting that this might need to be 'invisibly' handled, not using Vary:, but by any proxy clever enough to detect the non-conforming browser to then strip the request to deflate/gzip. At that point, the choice-of-two becomes obvious to all proxies and back end servers with this knowledge. If this is unknown to an earlier proxy, the client could get the broken deflate/gzip content, but that seems unavoidable. Honestly, I can't see a way to honor HTTP/1.1 cache negotiation goals while minimizing cache pollution. There isn't. So, optimize your cache, strip caching headers to downstream proxies. Maybe Waka can fix it.
Re: svn commit: r808226 - /httpd/httpd/branches/2.2.x/STATUS
minf...@apache.org wrote: URL: http://svn.apache.org/viewvc?rev=808226view=rev Log: Vote While attempting to promote, like this, svn merge is silently doing nothing, while svn diff works fine: graham-leggetts-macbook-pro-3:httpd-2.2 minfrin$ svn merge -c 777042 https://svn.apache.org/repos/asf/httpd/httpd/trunk graham-leggetts-macbook-pro-3:httpd-2.2 minfrin$ svn status graham-leggetts-macbook-pro-3:httpd-2.2 minfrin$ Am I doing something thunderously stupid, or does svn merge in 1.5.4 have issues I am not aware of? Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: svn commit: r797647 - /httpd/mod_fcgid/trunk/mod_fcgid/mod_fcgid.c
Jeff Trawick wrote: do you have any code yet to call this function? Once again, compiler warnings are our friend. Yes, this needs to be invoked, but it's a NTP, and the code I tossed was a new direction I wanted to go in, which would pick up all the PassEnv and other overrides, and set these all aside in a way that it would reinvoke the program again identically if a worker is lost. I then looked at the possibility of using httpd's API but that wasn't suitable either. So... back to the drawing board to flesh out this table before we go and invoke apr_proc_create. Thanks for drawing it to my attention.
