Re: Port range option in bind-address implemented?

Micah Cowan wrote: Yes, that appears to work quite well, as long as we seed it right; starting with a consistent Xâ‚€ would be just as bad as trying them sequentially, and choosing something that does not change several times a second (such as time()) still makes it likely that multiple invocatio

Re: --limit-percent N versus --limit-rate N% ?

Micah Cowan wrote: Also: does the current proposed patch deal properly with situations such as where the first 15 seconds haven't been taken up by part of a single download, but rather several very small ones? I'm not very familiar yet with the rate-limiting stuff, so I really have no idea. If

Re: config-post.h + gnulib breaks separate build dirs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > >> Could you be more specific? AFAICT, wget.h #includes the system headers >> it needs. Considering the config-post.h stuff went at the top of the >> sysdep.h, sysdep.h is already at t

Re: config-post.h + gnulib breaks separate build dirs

Micah Cowan <[EMAIL PROTECTED]> writes: > Could you be more specific? AFAICT, wget.h #includes the system headers > it needs. Considering the config-post.h stuff went at the top of the > sysdep.h, sysdep.h is already at the top of wget.h, OK, it should work then. The reasoning behind my worrying

Re: Port range option in bind-address implemented?

Micah Cowan <[EMAIL PROTECTED]> writes: > Yes, that appears to work quite well, as long as we seed it right; > starting with a consistent X₀ would be just as bad as trying them > sequentially, and choosing something that does not change several times > a second (such as time()) still makes it like

Re: config-post.h + gnulib breaks separate build dirs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > >> Is there any reason we can't move the contents of config-post.h into >> sysdep.h, and have the .c files #include "wget.h" at the top, before any >> system headers? > > wget.h *need

Re: config-post.h + gnulib breaks separate build dirs

Micah Cowan <[EMAIL PROTECTED]> writes: > Is there any reason we can't move the contents of config-post.h into > sysdep.h, and have the .c files #include "wget.h" at the top, before any > system headers? wget.h *needs* stuff from the system headers, such as various system types. If you take into