X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<SNT130-ds178639186E05EC4E561FB6E6780@phx.gbl>
From:	"Brien" <b_gs AT hotmail DOT com>
To:	<cygwin AT cygwin DOT com>
References:
In-Reply-To:
Subject:	RE: 1.7.1: sshd rsync fork problem
Date:	Thu, 31 Dec 2009 13:50:11 -0500
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

rebaseall might have done the trick (still need more time to be sure since
the problem was sporadic).

i don't really understand why my system needed it.  it's a clean install
plus openssh, rsync, psmisc, netcat, vim.

you might want to consider getting a blurb about "rebaseall" into the event
log entry for fork failures.

i am running under Windows 7... could that contribute?

thanks for the help.



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

- Raw text -