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
Date:	Tue, 9 Oct 2001 18:34:56 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT Com
Subject:	Re: Ignore the cygwin environment variable if child of a cygwin process?
Message-ID:	<20011009183456.A27407@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT Com
Mail-Followup-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> <027a01c15111$3a8a2370$0200a8c0 AT lifelesswks>
Mime-Version:	1.0
In-Reply-To:	<027a01c15111$3a8a2370$0200a8c0@lifelesswks>
User-Agent:	Mutt/1.3.21i

On Wed, Oct 10, 2001 at 08:24:57AM +1000, Robert Collins wrote:
>Log a informational to syslog and obey the new setting.
>This lets users hang themselves, but still tells them about it.

That's an idea.  We could theoretically have cygcheck replay any syslog entries.

Another thing that I was thinking was that we could have mkpasswd create a
"naive-user" entry.

If this entry existed then cygwin could issue warnings about certain standard user
errors.

Using /etc/passwd for this purpose is because we're already opening the /etc/passwd
file so checking it for this record (which could be first) wouldn't be a huge
performance penalty.

The downside is that we'd slow down slightly all cygwin apps to accomodate the
unknowledgeable users.

Just a thought...

cgf

- Raw text -