Re: host(1) prints errors to STDOUT

2015-08-13 Thread Craig Skinner
On 2014-10-15 Wed 16:25 PM |, Craig R. Skinner wrote: > On 2014-10-14 Tue 10:41 AM |, Theo de Raadt wrote: > > Unfortunately host is maintained upstream, in the bind codebase, > > by ISC. > > > > You should file your bug report there, because that is the right way > > to get change into the ecosys

Re: host(1) prints errors to STDOUT

2014-10-15 Thread Craig R. Skinner
On 2014-10-14 Tue 10:41 AM |, Theo de Raadt wrote: > Unfortunately host is maintained upstream, in the bind codebase, > by ISC. > > You should file your bug report there, because that is the right way > to get change into the ecosystem. > Submitted, with their GITWEB line number refs. "ISC's bu

Re: host(1) prints errors to STDOUT

2014-10-14 Thread Theo de Raadt
Unfortunately host is maintained upstream, in the bind codebase, by ISC. You should file your bug report there, because that is the right way to get change into the ecosystem. We could fix it here, and be different, then there will be even more problems. (Unfortunately, I expect them to mumble s

host(1) prints errors to STDOUT

2014-10-14 Thread Craig R. Skinner
$ host loopy.loo.found.not; print $? Host loopy.loo.found.not not found: 3(NXDOMAIN) 1 $ host loopy.loo.found.not > /dev/null; print $? 1 $ host loopy.loo.found.not 2>/dev/null; print $? Host loopy.loo.found.not not found: 3(NXDOMAIN) 1 There's a printf at line 429 of /usr/src/usr.sbin/bind/bin