This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Consensus: Tuning runtime behaviour with environment variables.

From: Stephan Bergmann <sbergman at redhat dot com>
To: "Carlos O'Donell" <carlos at redhat dot com>
Cc: GNU C Library <libc-alpha at sourceware dot org>, Roland McGrath <roland at hack dot frob dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, Andreas Jaeger <aj at suse dot com>, "Ryan S. Arnold" <ryan dot arnold at gmail dot com>, Andi Kleen <andi at firstfloor dot org>, David Miller <davem at davemloft dot net>, Siddhesh Poyarekar <siddhesh at redhat dot com>, Andreas Schwab <schwab at suse dot de>
Date: Wed, 29 May 2013 09:09:14 +0200
Subject: Re: Consensus: Tuning runtime behaviour with environment variables.
References: <51A58A92 dot 4050508 at redhat dot com>

On 05/29/2013 06:56 AM, Carlos O'Donell wrote:

- User changeable environment variables that impact library runtime
   behaviour is dangerous.

   * Could you specifically point out what you find dangerous?
     I see no more danger than we already face when adding a new
     API or reviewing code changes. How is this different
     than all of the other work we do?

One general problem of env vars is that they can all too easily affectprocesses they were not intended to affect (like when the target processspawns another process).


Stephan

Follow-Ups:
- Re: Consensus: Tuning runtime behaviour with environment variables.
  - From: Carlos O'Donell
- Re: Consensus: Tuning runtime behaviour with environment variables.
  - From: Carlos O'Donell

References:
- Consensus: Tuning runtime behaviour with environment variables.
  - From: Carlos O'Donell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]