Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 26 Apr 2005 19:06:20 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with 'cvs login'
Message-ID: <20050426230620.GA11486@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <959DF48BD1458D4C8DBFDAC8DF80D7F701D50094 AT europa DOT ats DOT sensis DOT com> <426EB5EA DOT 77D33CEE AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <426EB5EA.77D33CEE@dessent.net>
User-Agent: Mutt/1.5.8i

On Tue, Apr 26, 2005 at 02:43:06PM -0700, Brian Dessent wrote:
>"Rancier, Jeff" wrote:
>
>> |    passenv     = PATH
>
>I don't know if this applies in your situation, but if xinetd is
>stripping SYSTEMROOT from the child process' environment, then all
>socket functions in that process will fail.  I think recent versions of
>the cygwin1.dll have measures to prevent this from happening, but just
>for grins try adding SYSTEMROOT to the above and see if it makes any
>difference.

If that really does fix the problem then something is broken in CYGWIN.

Corinna fixed things so that this should no longer be a problem:

http://sources.redhat.com/ml/cygwin-announce/2004-11/msg00014.html

cgf

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