Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Fri, 17 Jan 2003 14:03:53 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: please try the latest snapshot Message-ID: <20030117190353.GA28900@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030117055216 DOT GA4969 AT redhat DOT com> <20030117154455 DOT GD2044 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030117154455.GD2044@tishler.net> User-Agent: Mutt/1.5.1i On Fri, Jan 17, 2003 at 10:44:55AM -0500, Jason Tishler wrote: >Chris, > >On Fri, Jan 17, 2003 at 12:52:16AM -0500, Christopher Faylor wrote: >> If I don't hear too many whines about this snapshot, it may become >> 1.3.19. > >The 2003-Jan-17 snapshot seems to fix the symlink problem that I >mentioned in: > > http://cygwin.com/ml/cygwin/2003-01/msg00827.html > >However, sshd is failing with the following in sshd.log: > > C:\cygwin\usr\sbin\sshd.exe: *** internal error > >I know that the above is not much to go on, but I thought that it was >better to start whining sooner rather that later. :,) I will try to dig >deeper. This should be fixed now. It was a simple mistake, as far as I could tell. How does the refreshed snapshot look? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/