From: Alive <alive4ever@live.com>
To: cygwin@cygwin.com
Subject: Re: Dig output not piping to xargs
Date: Sun, 26 Oct 2014 06:07:00 -0000 [thread overview]
Message-ID: <BLU436-SMTP542C599ED7913A9F735817E4910@phx.gbl> (raw)
In-Reply-To: <544C158C.9010006@kset.org>
On 10/26/2014 4:26 AM, Marko Božiković wrote:
> Hi all,
>
> 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.
>
> Thank you,
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)
```
I think it's a good idea to package `unbound` as an alternative to
`bind` for dns related tasks.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-10-26 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 21:26 Marko Božiković
2014-10-26 6:07 ` Alive [this message]
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
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=BLU436-SMTP542C599ED7913A9F735817E4910@phx.gbl \
--to=alive4ever@live.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).