Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #3965

Re: wget behavior

Show all headers | View raw

On Mon, 13 Feb 2017 20:08:37 +0000, MarkA wrote:

> On Mon, 13 Feb 2017 20:02:00 +0000, MarkA wrote:
> 
>> On Mon, 13 Feb 2017 11:32:59 +0000, William Unruh wrote:
>> 
>>> On 2017-02-12, MarkA <someone@somewhere.invalid> wrote:
>>>> On Sun, 12 Feb 2017 23:51:53 +0000, Richard Kettlewell wrote:
>>>>
>>>>> Mark A <deeptht69@gmail.com> writes:
>>>>>> Richard Kettlewell wrote:
>>>>>>> Mark A writes:
>>>>>>>> I'm using wget to download some large files from a download
>>>>>>>> server,
>>>>>>>> after several failed attempts to use Firefox's download function.
>>>>>>>> I can use the Firefox download function to get the URL of the
>>>>>>>> source, then paste that into wget, running in a Gnome terminal
>>>>>>>> window.  wget starts and shows its progress bar across the bottom
>>>>>>>> of the window. If I press "Enter", the progress bar freezes,
>>>>>>>> moves up one line, and is immediately replaced by a new one that
>>>>>>>> continues to update.
>>>>>>>>
>>>>>>>> After a few minutes, the progress bar stops updating.  If I press
>>>>>>>> "Enter", I get the command prompt.  "jobs" shows wget still
>>>>>>>> running,
>>>>>>>> now in the background.
>>>>>>> 
>>>>>>> I expect that there’s an ‘&’ in the URL and you didn’t quote it.
>>>>>>
>>>>>> No, no such characters in the URL.
>>>>> 
>>>>> Well, wget doesn’t generally put itself into the background for no
>>>>> reason.
>>>>
>>>> Hence my puzzlement.  Yet, there it is, with a big fat " &" after it,
>>>> when I type "jobs".
>>>>
>>>>
>>>>>> A few '%'s, though.  Besides, a malformed URL would cause it to
>>>>>> fail immediately.
>>>>> 
>>>>> ‘&’ doesn’t make the URL malformed.
>>>>
>>>> It does if it causes the software to misinterpret the URL.
>>>>
>>>>
>>>>
>>> Why not show us EXACTLY what command you typed.
>>> 
>>> 
>>> 
>>> 
>> Here it is (without line wraps in gnome terminal):
>> 
>> wget https://storage-ec2-462.sharefile.com/download.ashx?
>> dt=dtee4b0bcf14d24d04a797f03216a4d935&h=H%
>> 2bHB7RL13PQ9UWYn0spJbdXPG4Hp2mRtj1bIC4xfrG4%3d
>> 
>> Here is the command and response copied from the terminal:
>> toor@HPlaptop2013:/tmp$ wget https://storage-ec2-462.sharefile.com/
>> download.ashx?dt=dtee4b0bcf14d24d04a797f03216a4d935&h=H%
>> 2bHB7RL13PQ9UWYn0spJbdXPG4Hp2mRtj1bIC4xfrG4%3d [1] 3755
>> toor@HPlaptop2013:/tmp$ --2017-02-13 14:57:54--  https://storage-
>> ec2-462.sharefile.com/download.ashx?
> dt=dtee4b0bcf14d24d04a797f03216a4d935
>> Resolving storage-ec2-462.sharefile.com
>> (storage-ec2-462.sharefile.com)...
>> 34.197.226.34 Connecting to storage-ec2-462.sharefile.com (storage-
>> ec2-462.sharefile.com)|34.197.226.34|:443... connected.
>> HTTP request sent, awaiting response... 200 OK Length: 6313479914
>> (5.9G)
>> [application/zip]
>> Saving to: ‘download.ashx?dt=dtee4b0bcf14d24d04a797f03216a4d935’
> 
> Once the progress bar stops updating, and network traffic has dropped
> off, typing "jobs" gives:
> 
> toor@HPlaptop2013:/tmp$ jobs [1]+  Running                 wget
> https://storage-ec2-462.sharefile.com/
> download.ashx?dt=dtee4b0bcf14d24d04a797f03216a4d935 &
> toor@HPlaptop2013:/tmp$

New information: while doing something else, wget DID automatically 
resume, after a pause of perhaps 5 minutes:

toor@HPlaptop2013:/tmp$ 
download.ashx?dt=dtee4b0bcf14  27%[+++++++++
+==>                                     ]   1.64G  2.78MB/s    in 3m 
2s   

2017-02-13 15:38:42 (2.56 MB/s) - Read error at byte 
1765343232/6313479914 (Success). Retrying.

--2017-02-13 15:38:44--  (try: 3)  https://storage-ec2-462.sharefile.com/
download.ashx?dt=dtee4b0bcf14d24d04a797f03216a4d935
Connecting to storage-ec2-462.sharefile.com (storage-
ec2-462.sharefile.com)|34.197.226.34|:443... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 6313479914 (5.9G), 4548136682 (4.2G) remaining [application/zip]
Saving to: ‘download.ashx?dt=dtee4b0bcf14d24d04a797f03216a4d935’

<end quoted text>

So, it seems to be active in the foreground, sending a progress indicator 
to the terminal, until an error is made.  Then it quietly goes into the 
background, and after some time, resumes the download.  Not unreasonable 
behavior.

Thank you to everyone who replied to this thread, but I suppose it is 
working the way it should.  I just need to be more patient?

-- 
MarkA

You can safely assume that you have created God in your own image when it 
turns out that God hates all the same people you do.  -- Anne Lamott

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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