X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
From:	"Brian Wilson" <wilson AT ds DOT net>
To:	cygwin AT cygwin DOT com
Subject:	Re: SSH - Can't Login
Date:	Sun, 31 Oct 2010 12:50:05 -0500
Message-Id:	<20101031174620.M38121@ds.net>
In-Reply-To:	<AANLkTikGcLw8cqdh2ucZh8kKiVcd4VB4TVn=q0LZ5gTf@mail.gmail.com>
References:	<AANLkTi=y7UqM8aFci42oGYDfmC3tE4XofKoumhZ7h9q_ AT mail DOT gmail DOT com> <AANLkTi=pDfxw7ymUp-8yjHnAxAA+X-y0095qEFowp982 AT mail DOT gmail DOT com> <AANLkTi=D9e8Sv84tfWjDDuEsB755qT6XK==GM9jmFmB0 AT mail DOT gmail DOT com> <20101031170244 DOT M19842 AT ds DOT net> <AANLkTikGcLw8cqdh2ucZh8kKiVcd4VB4TVn=q0LZ5gTf AT mail DOT gmail DOT com>
X-OriginatingIP:	65.12.174.114 (wilson)
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

> On 31 October 2010 17:12, Brian Wilson wrote:
> > In my case the context was that suddenly ssh stopped working and would only
> > give the usage message no matter what I tried.  I ran the "cygcheck -svr" 
and
> > noted that I did not have the latest Cygwin (1.7.7) installed even though
> > running setup said there was nothing needed.
> 
> Which probably means that you'd tried to update the cygwin package
> while a Cygwin process was running, told it to skip it when setup.exe
> complained about it, and forgot to reboot to trigger the delayed
> update. There have been reports of the delayed update not working
> under some circumstances, but nothing definitive.

I did leave processes running when I did the update; good guess, but nope I did 
not skip the restart.  I choose the continue option and whenever I got the 
restart message, I did a restart.  I believe I have the latest setup as well, 
but am going to get a new one just in case.  Hopefully this won't happen in 
future.


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