Path: csiph.com!1.us.feeder.erje.net!feeder.erje.net!2.us.feeder.erje.net!news.glorb.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!spln!extra.newsguy.com!newsp.newsguy.com!news4 From: MarkA Newsgroups: comp.os.linux.networking Subject: Re: wget behavior Date: 14 Feb 2017 21:46:45 GMT Organization: NewsGuy - Unlimited Usenet $23.95 Lines: 27 Message-ID: References: <874lzzc7v0.fsf@LkoBDZeT.terraraq.uk> <2ff86561-47d6-4f3a-9436-d3c7c6ad864b@googlegroups.com> <87poinarxi.fsf@LkoBDZeT.terraraq.uk> <87wpctaltp.fsf@LkoBDZeT.terraraq.uk> <87r331aibn.fsf@LkoBDZeT.terraraq.uk> NNTP-Posting-Host: p7134b9ae5321616d0dd817212bfedd0437c4877ea0e0b1c1.newsdawg.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) X-Received-Bytes: 2135 X-Received-Body-CRC: 1713567675 Xref: csiph.com comp.os.linux.networking:3973 On Mon, 13 Feb 2017 21:58:18 +0000, Rick Jones wrote: > MarkA 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