On 10/31/07, Micah Cowan [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
On 10/30/07, Micah Cowan [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
Perhaps the little wget could be called wg.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
L Walsh wrote:
Don't know if anyone else has this problem, but sometimes when I'm
downloading large files (500MB; most recently 4.2GB), I want to change the
limit-rate without terminating the download and restarting.
For example, during the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
L Walsh wrote:
Honest -- I hadn't read all the threads before my post...
Great ideas Micah! :-)
On the idea of 2 wgets -- there is a clever way to get
by with 1. Put the optional functionality into separate
run-time loadable files. SGI's
Honest -- I hadn't read all the threads before my post...
Great ideas Micah! :-)
On the idea of 2 wgets -- there is a clever way to get
by with 1. Put the optional functionality into separate
run-time loadable files. SGI's Unix (and MS Windows) do this.
The small wget then checks to see which
Don't know if anyone else has this problem, but sometimes when I'm
downloading large files (500MB; most recently 4.2GB), I want to change the
limit-rate without terminating the download and restarting.
For example, during the day when I'm on my computer, I might not want it
to use more than
From: L Walsh
Say one runs the first wget. Lets say it is a simple 1-DVD download.
Then you start a 2nd download of another DVD. Instead of 2 copies
of wget running and competing with each other, what if the 2nd copy
told the 1st copy about the 2nd download, and the 2nd download
was
