On Mar 4, 2004, at 5:59 PM, Stas Bekman wrote:
Ideally you'd know what was the original command they have executed, but it's not possible. The most correct answer would be $0, since they will at least get to run the correct part if it was a bigger 'make test' or something else.
Right.
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 in my proposed wording:
% APACHE_TEST_STARTUP_TIMEOUT=420 make test
wont' work on C-shell complient systems, and hopefully they have /bin/env or a built-in 'env' function. So may be the above suggestion is the best.
Right.
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".
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. ;-)
Regards,
David
