httpd-test-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: [A-T patch] give a hint how to raise the timeout
Date Fri, 05 Mar 2004 02:18:33 GMT
David Wheeler wrote:

>> Alternatively we could say:
>>
>>   giving up after 121 secs. If you think that your system
>>   is slow or overloaded try again with a longer timeout value.
>>   For example set the env var APACHE_TEST_STARTUP_TIMEOUT to a longer 
>> value,
>>   e.g. 400 and repeat the last command.
>>
>> But can we trust the user to know how to set an env var? May be we 
>> should.
> 
> 
> Yeah, I think so, though you might want to say "environment variable", 
> instead.

Of course, I was just laze to type it out ;)

>> The only reason I mentioned -startup_timeout=420 is that if they have 
>> already used that option, APACHE_TEST_STARTUP_TIMEOUT won't take an 
>> effect, since command line options override env vars. But may be they 
>> will figure it out on their own.
> 
> 
> Well, you could still say "Or repeat the last command with the 
> -startup_timeout=420 option".

That would work, if the last command was 'make test' or any other wrapper.

>> Really, what I'm after is to give users as many hints as possible to 
>> get their side's problem resolved by themselves before they waste 
>> their and my time submitting a bug which is not.
> 
> 
> Of course, it's a good thing to do. I'm just nitpicking the wording. ;-)

And thank you for that ;)

-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Mime
View raw message