public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: bind-utils output not to stdout (was: Dig output not piping to xargs)
Date: Fri, 14 Nov 2014 13:39:00 -0000	[thread overview]
Message-ID: <20141114133936.GA29514@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20141114T140356-618@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

On Nov 14 13:25, Brian Inglis wrote:
> Alive <alive4ever <at> live.com> writes:
> > On 10/26/2014 4:26 AM, Marko Božiković wrote:
> >> I have recently noticed that dig +short output is not being properly piped to
> >> xargs (and it used to work)
> >> Doing something like:
> >> echo aaa | xargs -I {} echo {}
> >> works fine.
> >> However:
> >> dig +short www.google.com | xargs -I {} echo {}
> >> produces no output.
> >> I'm running Cygwin x64, tried a fresh install and it didn't help. Attached is
> >> the cygcheck output. Interestingly enough, cygcheck segfaults if I run it
> from
> >> bash. I had to run it from TCC to get the output file.
> 
> > I can confirm this behavior. `dig +short` always writes it output to the >
> terminal and cannot be redirected.
> > $ dig +short google.com
> > 74.125.68.101
> > 74.125.68.138
> > 74.125.68.100
> > 74.125.68.102
> > 74.125.68.139
> > 74.125.68.113
> > $ dig +short google.com | tee dig.txt
> > $ cat dig.txt
> > (no text is shown)
> > $ dig +short google.com 2>&1 | tee dig.txt
> > $ cat dig.txt
> > (no text is shown)
> 
> All bind-utils - host, nslookup, dig - output not to stdout or stderr - can
> not be redirected, but redirection suppresses output, with current update
> 9.9.6-2 but works with previous 9.9.5-3 and current cygwin release.

WFFM with the current Cygwin release 1.7.33.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-11-14 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 21:26 Dig output not piping to xargs Marko Božiković
2014-10-26  6:07 ` Alive
2014-11-14 13:25   ` bind-utils output not to stdout (was: Dig output not piping to xargs) Brian Inglis
2014-11-14 13:39     ` Corinna Vinschen [this message]
2014-11-14 14:39       ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141114133936.GA29514@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).