DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=ouqIIQKwK2wT8nPbJ0I0wkIp57L9c1+7DQIctpkGsnE
	yV0+kXjUfygtV5stj1C6rXQi0sqCzPET8hYOXji5kRcbpy4US6KcQT+wq0q33lpE
	fjcqynXt1X1GuKHYjY5tH0RhLsZBgXk363uH83WnGbjUdNZj5Ij0ZCWrPUwM0CxE
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <552ECFAC.7040003@winfirst.com>
Date: Wed, 15 Apr 2015 13:53:00 -0700
From: Mark Hansen <meh@winfirst.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: dig utility in bind-utils-9.9.7-1 returns no output
References: <CAFWoy7F6DMy4L8ccwOSztuJfKqPhkVW9TTsL2ZEBjvum-6hYsg@mail.gmail.com>	<CAFWoy7HKNuz8_nj9iHamGXzxvcFx-mtOSRPQJqn2OxGOpAmLmg@mail.gmail.com>	<1923978077.20150414135419@yandex.ru>	<CAFWoy7HGJSXhvjBraTqrw_XZ+6+JQFhJkrfANNGhz4wrXgQ=JQ@mail.gmail.com>	<552D7120.9000409@gmail.com>	<CAFWoy7FuWgcpOsv+fnC_wbrrx8rLJY8KcW86+kBJDzDFEoSuQw@mail.gmail.com>	<552D8C5E.2020208@winfirst.com>	<CAFWoy7FxE_jDKYLx_SNKayzzHOvr_BQb72WtFEQCXfApax0viQ@mail.gmail.com> <CAFWoy7HVZt8cTy5wpry+o4FrFTnJSYET1FEZCWL5Jnp7E7QNEw@mail.gmail.com>
In-Reply-To: <CAFWoy7HVZt8cTy5wpry+o4FrFTnJSYET1FEZCWL5Jnp7E7QNEw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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@gmail.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@winfirst.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