Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #3973
| From | MarkA <someone@somewhere.invalid> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: wget behavior |
| Date | 2017-02-14 21:46 +0000 |
| Organization | NewsGuy - Unlimited Usenet $23.95 |
| Message-ID | <o7vts512nhp@news4.newsguy.com> (permalink) |
| References | (7 earlier) <87wpctaltp.fsf@LkoBDZeT.terraraq.uk> <pan.2017.02.13.20.54.25@somewhere.invalid> <87r331aibn.fsf@LkoBDZeT.terraraq.uk> <pan.2017.02.13.21.48.24@somewhere.invalid> <o7ta5o$pja$1@news.hpeswlab.net> |
On Mon, 13 Feb 2017 21:58:18 +0000, Rick Jones wrote: > MarkA <someone@somewhere.invalid> wrote: >> I just ran the command again, this time single-quoting the URL. When it >> got to a point where the data stopped coming, wget stayed in the >> foreground. > > Quibble - before you quoted the '&' wget was "always" running in the > background, even before the point where data arrival stalled. Likely as > not when you were hitting return it was simply scrolling the terminal > display, and wget's updates were overwriting the shell prompt. > > rick jones Yes, I see that now. When the data stopped coming, wget stopped sending progress information, and it looked more like a usual, quiet background process. The other point I find interesting is that it seems to have downloaded the correct file, even after losing the characters following the '&' char in the URL. -- MarkA In politics and in life, ignorance is not a virtue. -- Barack Obama
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
wget behavior Mark A <deeptht69@gmail.com> - 2017-02-12 14:52 -0800
Re: wget behavior Richard Kettlewell <invalid@invalid.invalid> - 2017-02-12 23:22 +0000
Re: wget behavior Mark A <deeptht69@gmail.com> - 2017-02-12 15:45 -0800
Re: wget behavior Richard Kettlewell <invalid@invalid.invalid> - 2017-02-12 23:51 +0000
Re: wget behavior MarkA <someone@somewhere.invalid> - 2017-02-12 23:59 +0000
Re: wget behavior "Carlos E. R." <robin_listas@invalid.es> - 2017-02-13 02:09 +0100
Re: wget behavior Allodoxaphobia <knock_yourself_out@example.net> - 2017-02-13 01:41 +0000
Re: wget behavior "Carlos E. R." <robin_listas@invalid.es> - 2017-02-13 02:46 +0100
Re: wget behavior Richard Kettlewell <invalid@invalid.invalid> - 2017-02-13 09:18 +0000
Re: wget behavior William Unruh <unruh@invalid.ca> - 2017-02-13 11:32 +0000
Re: wget behavior MarkA <someone@somewhere.invalid> - 2017-02-13 20:02 +0000
Re: wget behavior MarkA <someone@somewhere.invalid> - 2017-02-13 20:08 +0000
Re: wget behavior MarkA <someone@somewhere.invalid> - 2017-02-13 20:42 +0000
Re: wget behavior Richard Kettlewell <invalid@invalid.invalid> - 2017-02-13 20:16 +0000
Re: wget behavior MarkA <someone@somewhere.invalid> - 2017-02-13 20:57 +0000
Re: wget behavior Richard Kettlewell <invalid@invalid.invalid> - 2017-02-13 21:31 +0000
Re: wget behavior MarkA <someone@somewhere.invalid> - 2017-02-13 21:51 +0000
Re: wget behavior Rick Jones <rick.jones2@hpe.com> - 2017-02-13 21:58 +0000
Re: wget behavior MarkA <someone@somewhere.invalid> - 2017-02-14 21:46 +0000
Re: wget behavior "Carlos E. R." <robin_listas@invalid.es> - 2017-02-13 23:37 +0100
Re: wget behavior MarkA <someone@somewhere.invalid> - 2017-02-14 21:50 +0000
csiph-web