bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] wget


From: Bryan Baas
Subject: Re: [Bug-wget] wget
Date: Mon, 20 Oct 2014 08:14:09 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

Fair enough.  Thank all for the timely replies.


-- 
Bryan Baas
Weyco IT
x1808
414 241 0499 (cell)

On 10/18/2014 10:44 AM, Yousong Zhou wrote:
> Hi, Bryan
> 
> Am 18.10.2014 21:43 schrieb "Bryan Baas" <address@hidden
> <mailto:address@hidden>>:
>>
>> Hi,
>>
>> I was wondering about the command output of wget.  I used a Java Runtime
>> exec and, although the wget process ended with a 0 completion code, the
>> results appeared in the error stream and not the output stream.
>>
>> As a further test, I executed the same command at the command line and
>> redirected output to a file using the > operator.  Upon completion the
>> file was empty, but the results scrolled down the screen.  This had me
>> thinking that the wget command itself is directing its regular output to
>> sderr instead of stdout.
> 
> Yes, that is the expected.  It is possible to set the output file to
> stdout with "-O -" in which case you do not want to see output of wget
> itself and the file content mangled together.
> 
>>
>> The results of the wget command, from what I could tell, weren't error
>> conditions but regular output from a successful execution.
>>
> 
> I think it is a convention that debug, informational, error, verbose
> output of unix programs be written to stderr.  However, the choice of
> redirecting stderr to whatever file descriptor users prefer is always
> available.
> 
> regards.
> 
>                 yousong
> 
>> Your feedback would be appreciated.
>>
>> regards,
>>
>>
>> --
>> Bryan Baas
>> Weyco IT
>> x1808
>> 414 241 0499 (cell)
>>
> 






reply via email to

[Prev in Thread] Current Thread [Next in Thread]