10

I am downloading data spread among multiple files that don't change once published.

Therefore --timestamping is not good enough, because it is constantly checking whatever resource is changed, which is, in my case, completely pointless.

--no-clobber would fit perfectly. Unfortunately it doesn't work with --convert-links for some reason.

Both --no-clobber and --convert-links were specified, only --convert-links will be used.

I hoped that --backup-converted would help but it changed nothing (it works for --timestamping.)

Why wget --convert-links --backup-converted --no-clobber --wait 1 https://example.com ignores --no-clobber and how could it be fixed?

  • Hitting that same problem today. How did you solve it? – Angelo Fuchs Jul 8 '17 at 20:43
  • 1
    @AngeloFuchs I never solved it (I would post answer if that would happen). In the end in my case redownloading fetched links was simpler than patching wget or switching to something else. – Mateusz Konieczny Jul 9 '17 at 9:14
-2

You cannot use both --convert-links and --no-clobber. You will get this message:

Both --no-clobber and --convert-links were specified, only --convert-links will be used.

wget can accomplish what you want, if you specify --convert-links and --timestamping. But this will only work if the target site supplies the file timestamp info in the response headers.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.