X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=QJ
	TEoK8I0az4prG3geAOIwGtg/1qAfXMSf50lfTuaOxCU07vLWWIXBkffimck6BOqm
	jpCnO2WnoNpKToQwC060OtKIv62MmWyW1VkRVMT/0d+g5NGnGU+RUqU04K3Efdaz
	bsBw7VtyXZ1TRDqdLrPkCo545oF3iAIGfpAxKr2AM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=v8iqkEsA
	O5JtTOPZGpCUog0316Q=; b=nz9K8QxvSQpbKxMGjrjIsuAzFpIB3NpiSwFZbmCR
	1tPGQhDTUabAaGQfPgtlVWSNXyDe8px8jKpzOs3B88MCW2ZotGGCBvvI9Y5oeR0M
	yU1vyJ0mLSZ/VuOhppudtEuNePNv8TwYX04DpLgwC2nAJllfI+dsQN913nojfTi0
	ryk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-ie0-f169.google.com
MIME-Version: 1.0
X-Received: by 10.107.35.70 with SMTP id j67mr5091686ioj.51.1429290446035; Fri, 17 Apr 2015 10:07:26 -0700 (PDT)
In-Reply-To: <CAFWoy7HftTvrBM2VxT1fxBsit7u-4gi4wnWCx56P6Ls_S8FU4g@mail.gmail.com>
References: <CAFWoy7F6DMy4L8ccwOSztuJfKqPhkVW9TTsL2ZEBjvum-6hYsg AT mail DOT gmail DOT com>	<CAFWoy7HKNuz8_nj9iHamGXzxvcFx-mtOSRPQJqn2OxGOpAmLmg AT mail DOT gmail DOT com>	<1923978077 DOT 20150414135419 AT yandex DOT ru>	<CAFWoy7HGJSXhvjBraTqrw_XZ+6+JQFhJkrfANNGhz4wrXgQ=JQ AT mail DOT gmail DOT com>	<552D7120 DOT 9000409 AT gmail DOT com>	<CAFWoy7FuWgcpOsv+fnC_wbrrx8rLJY8KcW86+kBJDzDFEoSuQw AT mail DOT gmail DOT com>	<552D8C5E DOT 2020208 AT winfirst DOT com>	<CAFWoy7FxE_jDKYLx_SNKayzzHOvr_BQb72WtFEQCXfApax0viQ AT mail DOT gmail DOT com>	<CAFWoy7HVZt8cTy5wpry+o4FrFTnJSYET1FEZCWL5Jnp7E7QNEw AT mail DOT gmail DOT com>	<552ECFAC DOT 7040003 AT winfirst DOT com>	<CAFWoy7HftTvrBM2VxT1fxBsit7u-4gi4wnWCx56P6Ls_S8FU4g AT mail DOT gmail DOT com>
Date: Fri, 17 Apr 2015 11:07:25 -0600
Message-ID: <CAFWoy7EowK6mkAvEmgbNMdDVvf_vieyaWmhm8XLQKJJmyYeA9A@mail.gmail.com>
Subject: Re: dig utility in bind-utils-9.9.7-1 returns no output
From: Keith Christian <keith1christian AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

Yaakov, Brian, Andrey, Marco, and Mark -----

I updated Cygwin this morning, and now: "dig works!  I have no idea why!"

"cksum /usr/bin/dig /bin/dig" reports the same checksums as before,
and "cygcheck dig" produces the same output as before.

Baffling.

Thanks to all of you for the suggestions.

On Wed, Apr 15, 2015 at 4:19 PM, Keith Christian
<keith1christian AT gmail DOT com> wrote:
> Thanks Mark, but I tried both of those early in my attempts without
> success.  Good suggestion, though.
>
> On Wed, Apr 15, 2015 at 2:53 PM, Mark Hansen <meh AT winfirst DOT com> wrote:
>> On 4/15/2015 12:02 PM, Keith Christian wrote:
>>>
>>> cygcheck attachment is too large according to sourceware.
>>>
>>> What specific parts of cygcheck are needed to help troubleshoot this?
>>>
>>> Keith
>>>
>>> On Wed, Apr 15, 2015 at 12:55 PM, Keith Christian
>>> <keith1christian AT gmail DOT com>  wrote:
>>>>
>>>>  Both /usr/bin/dig and /bin/dig run the same program:
>>>>
>>>>> cksum /usr/bin/dig /bin/dig
>>>>
>>>>  680300229 2202141 /usr/bin/dig
>>>>  680300229 2202141 /bin/dig
>>>>
>>>>  Attached cygcheck_s_r_v_kvc.txt.
>>
>>
>> I'm sorry - I could be completely off-base here. What I meant was can you
>> try running
>> '/usr/bin/dig' (providing the full path to the application) rather than by
>> just running 'dig'
>> just in case there is some other 'dig' on your path (or shell aliases) which
>> might be running
>> rather than the actual /usr/bin/dig command.
>>
>> In previous messages, your examples were running 'dig' (without the full
>> path) so it wasn't
>> clear which dig you were actually getting.
>>
>> Good luck.
>>
>>
>>>>
>>>>  On Tue, Apr 14, 2015 at 3:53 PM, Mark Hansen<meh AT winfirst DOT com>  wrote:
>>>>>
>>>>>  Are you sure that you're getting the correct dig executable? Is it
>>>>> possible
>>>>>  that something else in
>>>>>  your path or alias list is getting hit? Perhaps you can try
>>>>> /usr/bin/dig
>>>>>  just to be sure?
>>
>>
>> --
>> 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
>>

--
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