[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-wget] Timestamping vs incomplete downloads

From: Dave Warren
Subject: [Bug-wget] Timestamping vs incomplete downloads
Date: Mon, 22 Oct 2018 17:49:12 -0600
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

Currently when a download with timestamping enabled gets interrupted, the timestamp of the resulting file ends up being the current time and when wget is re-executed after connectivity is restored the local file is then seen as newer and skipped.

robocopy handles this a little differently, by setting a date far in the past as a way of ensuring that on a subsequent execution the transfer can be resumed.

Is there a better way to handle this situation in wget? A way to force an old date on the file? I'd be happy with a fixed "in the past" date, the service supplied date minus a second, etc. Or some way to detect that the file is incomplete (too small) on a subsequent run?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]