Hi, Am 21.12.2013 um 10:24 schrieb Yousong Zhou <[email protected]>: > In my situation, wget was trigger on the remote machine like the > following: > > wget -O - --start-pos "$OFFSET" "$URL" | nc -lp 7193 > > Then on local machine, I would download with: > > nc localhost 7193 > > Before these, a local forwarding tunnel has been setup with ssh to make > this possible. So in this case, there was no local file on the machine > where wget was triggerred and `--continue' will not work. I am sure > there are other cases `--start-pos' would be useful and that > `--start-pos' would make wget more complete.
When I just look at your problem it seems to be easier to set up the tunnel slightly different and pull with standard wget. If the URL looks like http://<host>:<port>/<rest> and you set up the tunnel with ssh -L 7193:<host>:<port> <machine-where-you-called-wget-previously> and then just wget http://localhost:7193/<rest> the range requests would be sent by wget just fine to the initial server and you could also safely use -c on further wget invocations (or with proper values for -t / -T automatically). Best regards -- Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896
smime.p7s
Description: S/MIME cryptographic signature
