delorie.com/archives/browse.cgi | search |
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: | <034a01c15113$dcf867a0$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> <027a01c15111$3a8a2370$0200a8c0 AT lifelesswks> <20011009183456 DOT A27407 AT redhat DOT com> |
Subject: | Re: Ignore the cygwin environment variable if child of a cygwin process? |
Date: | Wed, 10 Oct 2001 08:43:48 +1000 |
MIME-Version: | 1.0 |
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:49:55.0750 (UTC) FILETIME=[B72D9C60:01C15114] |
----- Original Message ----- From: "Christopher Faylor" <cgf AT redhat DOT com> To: <cygwin-developers AT cygwin DOT Com> Sent: Wednesday, October 10, 2001 8:34 AM Subject: Re: Ignore the cygwin environment variable if child of a cygwin process? > 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. > The other downside is that once a user is knowledgable, it doesn't mean they will *stay* that way. If we change the safe rules - even slightly - we will need to introduce 'naive_user2'. :[ Rob
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |