On 05/22/2017 05:19 AM, Barry Kauler wrote: > On 5/21/17, Tim Rühsen <tim.rueh...@gmx.de> wrote: >> On Sonntag, 21. Mai 2017 10:06:28 CEST Barry Kauler wrote: >>> Hi guys, >>> I recently upgraded wget to 1.19.1, but have discovered that it has >>> broken some of my scripts. >>> >>> These are scripts that expect output on stderr. For example, have >>> "wget ... 2> logfile" or "wget ..... 2>&1 | .... " >>> >>> Instead, I just get text message "Redirecting output to ‘wget-log.1’", >>> and get a logfile at ~/wget-log.1 >> >> I can't reproduce that with 1.19.1, also not with the command posted at the >> >> link below. >> What system are you on and what is your complete command line ? >> >> With Best Regards, Tim >> >>> Is there a good reason for this change? >>> >>> If not, I would like the old behaviour back please. >>> >>> I see someone else has posted about this: >>> https://www.makemkv.com/forum2/viewtopic.php?f=3&t=15885 >>> >>> Regards, >>> Barry Kauler >> > > This is the line in a shell script, that has worked for years, now broken: > > LANG=C wget -4 -t 2 -T 20 --waitretry=20 --spider -S "${URLSPEC}" > > /tmp/download_file_spider.log1 2>&1 > > I am running an experimental distribution, compiled in OpenEmbedded > (that Yocto uses). > > I notice commits late in 2016 that look like they might be the cause. > HOWEVER, the problem has disappeared.
Which commits are these ?
Git blame doesn't find a code change for fork_to_background() since it
was introduced in 1999.
If you use and explicit logfile (-o / --output-file), that code for
creating 'wget-log' isn't triggered.
'man wget':
" -b
--background
Go to background immediately after startup. If no output
file is specified via the -o, output is redirected to wget-log.
"
With Best Regards, Tim
signature.asc
Description: OpenPGP digital signature
