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" 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: References: <20101031170244 DOT M19842 AT ds DOT net> X-OriginatingIP: 65.12.174.114 (wilson) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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