From e499b2354346776a26857c9e5002f12bd6e6d0ef Mon Sep 17 00:00:00 2001 From: nodiscc Date: Thu, 3 Aug 2017 16:24:41 +0200 Subject: [PATCH] clarify TIMEOUT option purpose This option does not set a timeout for establishing connections (non-responding hosts): instead it is the maximum allowed time for a page download. If the page is large, setting a low timeout value may cause the transfer to abort, even if the transfer speed is good enough. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 62da5100..afca5c29 100644 --- a/README.md +++ b/README.md @@ -95,7 +95,7 @@ env CHROME_BINARY=google-chrome-stable RESOLUTION=1440,900 FETCH_PDF=False ./arc - path to wget: `WGET_BINARY` values: [`wget`]/`/usr/local/bin/wget`/`...` **Archive Options:** - - download timemout: `TIMEOUT` values: [`60`]/`30`/`...` + - maximum allowed download time per link: `TIMEOUT` values: [`60`]/`30`/`...` - archive methods: `FETCH_WGET`, `FETCH_PDF`, `FETCH_SCREENSHOT`, `FETCH_FAVICON`, `SUBMIT_ARCHIVE_DOT_ORG` values: [`True`]/`False` - archive images/css/js: `FETCH_WGET_REQUISITES` values: [`True`]/`False` (True is highly recommended) - screenshot: `RESOLUTION` values: [`1440,900`]/`1024,768`/`...`