Dan Jacobson <[EMAIL PROTECTED]> writes:
> H> Maybe it should rather vary between 0.5*wait and 1.5*wait?
> There you go again making assumptions about what the user wants.
Simply looking for a more reasonable default.
H> Maybe it should rather vary between 0.5*wait and 1.5*wait?
There you go again making assumptions about what the user wants.
H> I think it'd be a shame to spend more arguments on such a rarely-used
H> feature.
--random-wait[=a,b,c,d...] loaded with lots of downwardly compatible
Dan Jacobson <[EMAIL PROTECTED]> writes:
> "--random-wait causes the time between requests to vary between 0 and
> 2 * wait seconds, where wait was specified using the --wait option, "
>
> So one can no longer specify a minimum wait time!
Good point. Maybe it should
"--random-wait causes the time between requests to vary between 0 and
2 * wait seconds, where wait was specified using the --wait option, "
So one can no longer specify a minimum wait time! The 2 and at least
the 0 should be user configurable floating numbers.
The man page doesn't say what will happen if one specifies
--random-wait but no --wait has been used.
Perhaps just say under --wait that --wait=0 if not set.
Obviously, that's another possibility.
Also (with either one) would be nice something like
--random-wait=20%
wait from 80..120% of the wait time, calculated after all the
commandline and wgetrc and system wgetrc have been evaluated.
Would be nice, dump random-wait = 50% in the wgetrc an
hi!
--random-wait=20 between 0 and 20 secs.
--random-wait=20..30 between 20 and 30 (closed-closed) :)))
or of cource:
--random-wait=20-30
P! Vladi.
Herold Heiko wrote:
>
> I couldn't test that option yet,
>
> but it seems to use 0 .. 2*opt.wai
I couldn't test that option yet,
but it seems to use 0 .. 2*opt.wait for it's random waiting.
What if somebody wants to wait a longer time with different random
intervall... say wait from 20..30 seconds ?
Possibly it would be better giving random-wait a numeric option, and use
some
