X-Spam-Check-By: sourceware.org
Date: Mon, 05 Jun 2006 12:09:43 +0100
From: Robin Walker <rdhw AT cam DOT ac DOT uk>
Reply-To: Robin Walker <rdhw AT cam DOT ac DOT uk>
To: cygwin AT cygwin DOT com
Subject: Re: sshd: fork of unprivileged child failed
Message-ID: <8F117F75630F94683968A754@qjunbur.quns.cam.ac.uk>
In-Reply-To: <44835C24.30802@cygwin.com>
References: <BEA70E0A3FEDAAAA547BDE99 AT qjunbur DOT quns DOT cam DOT ac DOT uk>  <44835C24 DOT 30802 AT cygwin DOT com>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 04 June 2006 18:18 -0400 "Larry Hall (Cygwin)" wrote:

> Robin Walker wrote:
>> In the Windows Application Log there are, for each failed connection
>> attempt, entries of the form:
>>
>> sshd: PID xxxx: fatal: fork of unprivileged child failed.
>
> Did you try a recent snapshot?

If, by "snapshot", you mean System Restore Point, then the problems began 
too long ago for a restore point still to exist.  I have been searching for 
solutions for some months already.

> Please read and follow the problem reporting guidelines found at:
> <http://cygwin.com/problems.html>

I couldn't see anything there that addresses this problem.  I included a 
cygcheck output in a previous post in this thread.  I have already spent 
some months struggling with this before coming to this list, and Googled 
every likely search term.  The searches show some other users had a similar 
problem, but cured it with a rebaseall.  That worked once for me, but no 
longer.

> Think about things that have changed about the time things stopped working
> for you.  This includes things both a part of and external to Cygwin.

Most likely, it was a Cygwin update.  sshd worked OK during most of 2005, 
but has not worked since I updated Cygwin early in 2006.  I don't use ssh 
on a daily basis, and it took some time to notice that connections were 
failing.

Is there any way I can get a previous version of cygwin1.dll to check 
against?

-- 
Robin Walker (Junior Bursar), Queens' College, Cambridge CB3 9ET, UK
rdhw AT cam DOT ac DOT uk  http://www.queens.cam.ac.uk/  Tel:+44 1223 335528

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/