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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding
	:reply-to; q=dns; s=default; b=lbWwuOdD+XdDSrIrMNBLGYYzrrTDS4a12
	u7g4x9s7MONEsdEglNeNo8FgPxib0doFb3kU9ua/XTzxJKDV6NPr0RhaRLLKFGkW
	kpeb/ylGiMhc9ZmcyCnvdxGdowPxj/O05kXPDiEw3v/5Lsi1qKvnm2ZXgSFI2BGj
	xFM8hobF98=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding
	:reply-to; s=default; bh=6WAt5MFIqYYeYCzHc/PQukUe6AM=; b=RDCYG0h
	cWvFwhtvyeoUfBm06rcoBOIQ7k0KTHWVr7lWiemVPFOgtOFFqhmx/YxmhF4nSob7
	uDhSR8PJTAfA0n/2bYNz6ePNgf1sjqrFUkq/1dSNja8x3o/9xyJQM8CnppqtSG4L
	EGEl8BJYNYdF5yoHg3VFArTGupLMVUy5c3po=
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=0.8 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	qmta14.emeryville.ca.mail.comcast.net
Message-ID:	<53430FAA.9010409@acm.org>
Date:	Mon, 07 Apr 2014 13:50:50 -0700
From:	David Rothenberger <daveroth AT acm DOT org>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.7.29-2: Exception from cygwin_gethostname
References:	<5342F343 DOT 6050300 AT acm DOT org> <20140407190942 DOT GU2061 AT calimero DOT vinschen DOT de> <5343035E DOT 4000106 AT cygwin DOT com>
In-Reply-To:	<5343035E.4000106@cygwin.com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Larry Hall (Cygwin) wrote:
> On 4/7/2014 3:09 PM, Corinna Vinschen wrote:
>> On Apr  7 11:49, David Rothenberger wrote:
>>> I'm having a problem doing hostname resolution on one of my Windows
>>> 7 64 machines after updating cygwin to 1.7.29-2. I first noticed it
>>> with ssh. I get an error whenever I try to ssh to any machine using
>>> a hostname; it complains the hostname cannot be resolved.
>>>
>>> An strace of ssh shows an exception occuring right after the call to
>>> cygwin_gethostname is logged.
>>>
>>>     96   58624 [main] ssh 3536 cygwin_gethostname: name daver-pc
>>> --- Process 3536, exception 000006ba at 000007FEFDD4940D
>>>    860   59484 [main] ssh 3536 __set_errno: void san::leave():315
>>> setting errno 14
>>
>> Exception 0x6ba is "The RPC server is unavailable".  I have no idea why
>> this exception is generated at all on your machine.  Usually this is a
>> first-chance exception only, which can be ignored, but this is the first
>> time I ever saw this and in the above scenario there's no such exception
>> expected, so it doesn't get ignored.
>>
>> Oh well, it would have been helpful if this had been encountered last
>> week :(
> 
> Good point.  David, can you go back to last week and see if you can still
> reproduce it? ;-)

I wish! There were a few important changes to the system starting last
Friday and I dearly wish I could go back to before those changes.

On Friday, I accidentally installed OpenCandy, a PUP adware "program". I
spent some time on Saturday cleaning that with a host of free malware
removals. This removed some registry keys, but I'm pretty sure it was
all safe. Pretty sure...

Also on Saturday I replaced two old HDDs with SSDs. This made my system
a lot faster, but I haven't seen any problems associated with it aside
from the OS complaining about not getting a network connection right
after it boots. I think this is just because it boots so much faster now.

I /should/ have tested the snapshots when the call went out. I wished I
did now, because then I would know if this issue was related to any of
the problems I had late last week. This is a work machine and we're
super-busy, so I was hesitant to experiment with snapshots. But I
learned my lesson; I'll be testing snapshots when Chris or Corinna ask
for testing from now on, on all my machines.


-- 
David Rothenberger  ----  daveroth AT acm DOT org

"It's when they say 2 + 2 = 5 that I begin to argue."
                -- Eric Pepke

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

- Raw text -