Skip to main content
added 16 characters in body; added 9 characters in body; added 7 characters in body
Source Link
mikeserv
  • 59.4k
  • 10
  • 122
  • 242

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

{ find . ; catsed 's/.*/.&/' list.file ; } | 
    sort | uniq -u

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

{ find ; cat ./file ; } | sort -u

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

{ find . ; sed 's/.*/.&/' list.file ; } | 
    sort | uniq -u
added 62 characters in body; deleted 385 characters in body
Source Link
mikeserv
  • 59.4k
  • 10
  • 122
  • 242

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

find{ /./path/from/rootfind |; 
sedcat 's:/./path/from/root/to/base/dir(.*):\\|\1|d:'file |
sed; -f} /dev/stdin| ./path/to/listsort -u

That should take a list from find of all of the files you currently have, parse its output with sed into a sed delete command, then pass those delete commands over to another sed which will use the |pipe as its script.

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

find /./path/from/root | 
sed 's:/./path/from/root/to/base/dir(.*):\\|\1|d:' |
sed -f /dev/stdin ./path/to/list

That should take a list from find of all of the files you currently have, parse its output with sed into a sed delete command, then pass those delete commands over to another sed which will use the |pipe as its script.

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

{ find ; cat ./file ; } | sort -u
added 32 characters in body
Source Link
mikeserv
  • 59.4k
  • 10
  • 122
  • 242

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

find /./path/from/root | 
sed 's:/./path/from/root/to/base/dir(.*):\\|\1|d:' |
sed -f /dev/stdin ./path/to/list

That should take a list from find of all of the files you currently have, parse its output with sed into a sed delete command, then pass those delete commands over to another sed which will use the |pipe as its script.

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

find /./path/from/root | 
sed 's:/./path/from/root/to/base/dir(.*):\\|\1|d:' |
sed -f /dev/stdin ./path/to/list

I don't think you need to use wget's recursive downloading options because you already have a list of the files that need downloading:

wget --input-file=./path/to/your/list --base=URL

In this way you would just follow the list in the first place, and so every file downloaded would be just the next in the list. So you could always find your progress by merely checking against the last file downloaded and its position in the list.

But if that doesn't work:

find /./path/from/root | 
sed 's:/./path/from/root/to/base/dir(.*):\\|\1|d:' |
sed -f /dev/stdin ./path/to/list

That should take a list from find of all of the files you currently have, parse its output with sed into a sed delete command, then pass those delete commands over to another sed which will use the |pipe as its script.

added 32 characters in body
Source Link
mikeserv
  • 59.4k
  • 10
  • 122
  • 242
Loading
added 124 characters in body
Source Link
mikeserv
  • 59.4k
  • 10
  • 122
  • 242
Loading
Source Link
mikeserv
  • 59.4k
  • 10
  • 122
  • 242
Loading