Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <027a01c15111$3a8a2370$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT Com>
References: <20011009133655 DOT A25333 AT redhat DOT com> <3BC338F3 DOT 3FDF0FE9 AT yahoo DOT com> <20011009141754 DOT C25375 AT redhat DOT com>
Subject: Re: Ignore the cygwin environment variable if child of a cygwin process?
Date: Wed, 10 Oct 2001 08:24:57 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 09 Oct 2001 22:31:04.0303 (UTC) FILETIME=[14C87FF0:01C15112]


----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
To: <cygwin-developers AT cygwin DOT Com>
Sent: Wednesday, October 10, 2001 4:17 AM
Subject: Re: Ignore the cygwin environment variable if child of a cygwin
process?


> On Tue, Oct 09, 2001 at 01:50:43PM -0400, Earnie Boyd wrote:
> >Christopher Faylor wrote:
> >>
> >> I keep seeing people who have set the CYGWIN environment variable
from the bash
> >> shell.  This causes strange problems.
> >>
> >> I wonder if it would be worthwhile to ignore the CYGWIN environment
variable
> >> if it is set in a process that is a child of a cygwin process.
> >>
> >> The downside is that there are probably some situations where it
> >> actually works ok to do this and that we'll end up screwing up
people
> >> who know what they're doing.
> >>
> >> We could just issue a warning but I hate for cygwin to be noisy in
these kinds
> >> of situations.
> >>
> >> Any thoughts?

Log a informational to syslog and obey the new setting.

This lets users hang themselves, but still tells them about it.

Rob