X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
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>
Date: Sun, 31 Oct 2010 17:41:21 +0000
Message-ID: <AANLkTin0eOuLcbOJNOu_ca5dP8W_Lx7aN8x_8TMm1JW6@mail.gmail.com>
Subject: Re: SSH - Can't Login
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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:39, Andy Koppe wrote:
> On 31 October 2010 17:12, Brian Wilson wrote:
>> In my case the context was that suddenly ssh stopped working and would o=
nly
>> give the usage message no matter what I tried. =C2=A0I 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.

Also, make sure you're using the latest setup.exe. A problem with the
handling of in-use packages was fixed earlier this year.

Andy

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