From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Cc: slint@freelists.org
Subject: wget downloads
Date: Wed, 18 Mar 2020 17:51:13 -0400 [thread overview]
Message-ID: <alpine.NEB.2.21.2003181743480.22723@panix1.panix.com> (raw)
the best way I've found to do wget downloads outside of sourceforge.net is
to use:
wget -bc url.
The reason for this is if wget-log doesn't exist on your user directory,
wget will create it and write its download progress into wget-log. If
wget-log exists, wget-log.1 will get created and written to for the
present download.
The suffix number increases if the last one is present so you could get a
bunch of wget-log files in your user directory if you don't manage them.
The reasons you want wget-log are two.
First you can check if the download is complete with:
grep -i saved wget-log
If grep returns nothing, it means either a download failed or hasn't yet
finished.
If grep returns a line of information with the word saved in it, it means
your download is complete.
The second reason is you can check the progress of your download with:
wc -l wget-log
That will return a number.
If you repeat that command and get a higher number back, your download is
progressing.
If you don't use wget -bc url, you get a mess on your screen and no
ability to check completion and progress of your download.
--
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.21.2003181743480.22723@panix1.panix.com \
--to=blinux-list@redhat.com \
--cc=slint@freelists.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).