Re: [patch] more robust startup + counting
On Wed, 5 Dec 2001, Stas Bekman wrote: I suggest having an APACHE_TEST_CRON_MODE env var which will also replace APACHE_TEST_NO_COLOR. Sounds OK? i'd just rather have a different name. this'll be useful for more than cron. in fact i'd be happy to stick with APACHE_TEST_NO_COLOR.
Re: [patch] more robust startup + counting
Doug MacEachern wrote: On Wed, 5 Dec 2001, Stas Bekman wrote: I suggest having an APACHE_TEST_CRON_MODE env var which will also replace APACHE_TEST_NO_COLOR. Sounds OK? i'd just rather have a different name. this'll be useful for more than cron. in fact i'd be happy to stick with APACHE_TEST_NO_COLOR. so be it. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: [patch] more robust startup + counting
Doug MacEachern wrote:
one thing we need to fix with this new feature is the ability to turn
off this output. for the same reason we have $ENV{APACHE_TEST_NO_COLOR}
to turn off the colors. for when t/TEST output is redirected to a file,
like from a cron job. at the moment t/TEST test.log outputs a bunch of
waiting for server to start: 00:nn. maybe have one ENV var to turn off
all things like this, APACHE_TEST_SIMPLE_OUTPUT or something.
How about APACHE_TEST_BATCH_OUTPUT?
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
All right everyone! Step away from the glowing hamburger!
Re: [patch] more robust startup + counting
Rodent of Unusual Size wrote: Stas Bekman wrote: Rodent of Unusual Size wrote: Eh, I'm now getting this on Win32: perl t\TEST apache.exe -v failed: Bad file descriptor at Apache-Test/lib/Apache/TestConfig.pm line 687. I don't think this has anything to do with this. If the line counter wasn't shifted, you've got a broken Symbol::gensym. I ran it this morning witk a checkout from a couple of days ago. No worries. I updated this morning and ran it again, with the results above. The only file changed by the update was perl-framework/Apache-Test/lib/Apache/TestServer.pm Nothing else has happened on my system; no Perl module changes or anything. Ergo, the change to the above file is what broke my harness. And this problem still has nothing to do with the latest fix. Just for the kicks try to replace this version with 1.41 or 1.40 or TestServer.pm and you will see. -- _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: [patch] more robust startup + counting
this broke something. i keep getting: % t/TEST ... waiting for server to start: ok (waited 0 secs) ... still waiting for server to warm up: ok (waited 1 secs) failed to start server! (please examine t/logs/error_log) and yet the server is running.
Re: [patch] more robust startup + counting
That would be my patch to detect an 'extra unused arg' to httpd. As it is, there was no quick-fix I could see, so I've reverted. Update your httpd-2.0 cvs - Original Message - From: Doug MacEachern [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 1:34 AM Subject: Re: [patch] more robust startup + counting this broke something. i keep getting: % t/TEST ... waiting for server to start: ok (waited 0 secs) ... still waiting for server to warm up: ok (waited 1 secs) failed to start server! (please examine t/logs/error_log) and yet the server is running.
Re: [patch] more robust startup + counting
William A. Rowe, Jr. wrote: That would be my patch to detect an 'extra unused arg' to httpd. As it is, there was no quick-fix I could see, so I've reverted. Update your httpd-2.0 cvs In this particular case it was a bug in my latest patch. It's fixed now. - Original Message - From: Doug MacEachern [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 1:34 AM Subject: Re: [patch] more robust startup + counting this broke something. i keep getting: % t/TEST ... waiting for server to start: ok (waited 0 secs) ... still waiting for server to warm up: ok (waited 1 secs) failed to start server! (please examine t/logs/error_log) and yet the server is running. -- _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: [patch] more robust startup + counting
Stas Bekman wrote: In this particular case it was a bug in my latest patch. It's fixed now. Eh, I'm now getting this on Win32: perl t\TEST apache.exe -v failed: Bad file descriptor at Apache-Test/lib/Apache/TestConfig.pm line 687. ?? -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ All right everyone! Step away from the glowing hamburger!
Re: [patch] more robust startup + counting
Stas Bekman wrote: Rodent of Unusual Size wrote: Eh, I'm now getting this on Win32: perl t\TEST apache.exe -v failed: Bad file descriptor at Apache-Test/lib/Apache/TestConfig.pm line 687. I don't think this has anything to do with this. If the line counter wasn't shifted, you've got a broken Symbol::gensym. I ran it this morning witk a checkout from a couple of days ago. No worries. I updated this morning and ran it again, with the results above. The only file changed by the update was perl-framework/Apache-Test/lib/Apache/TestServer.pm Nothing else has happened on my system; no Perl module changes or anything. Ergo, the change to the above file is what broke my harness. -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ All right everyone! Step away from the glowing hamburger!
Re: [patch] more robust startup + counting
Rodent of Unusual Size wrote: Stas Bekman wrote: I don't think this has anything to do with this. If the line counter wasn't shifted, you've got a broken Symbol::gensym. The failing line is: open $handle, $cmd| or die $cmd failed: $!; -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ All right everyone! Step away from the glowing hamburger!
