X-Recipient: archive-cygwin@delorie.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: <20101031170244.M19842@ds.net> References: <20101031170244.M19842@ds.net> Date: Sun, 31 Oct 2010 17:39:43 +0000 Message-ID: Subject: Re: SSH - Can't Login From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 31 October 2010 17:12, Brian Wilson wrote: > In my case the context was that suddenly ssh stopped working and would on= ly > 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. 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