Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Andrew Schulman <andrex AT alumni DOT utexas DOT net>
Subject:  Re: who is setting the NAME variable in bash?
Date:  Thu, 25 Aug 2005 14:41:25 -0400
Lines: 26
Message-ID:  <4t3sg1pet8ta5so08m49cmev4mlqt327fl@4ax.com>
References:  <0vurg158jdhbm2c8s27sis4tderbdk8ije AT 4ax DOT com> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050825134923 DOT 06e074f8 AT pop DOT prospeed DOT net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
X-IsSubscribed: yes

> >Any suggestions for how I can figure out who's setting NAME?  I want
> >to make them stop.
> 
> Look in your Windows environment.  Apparently someone set it for you there.
> If you don't want it, you can try removing it.  Windows doesn't require it
> either so whatever added it is local to your installation  So you'll need
> to determine the overall validity/usefulness of this variable yourself.

Thanks.  I forgot to mention it in my first post, but I already
checked this.  NAME isn't set in the Windows environment, either
System or User varieties.

However, your suggestion prompted me to look and see which processes
have NAME set in their environments.  (TaskInfo will show you the
environment of every running process.)  I found that Explorer.exe has
NAME set, and of course all of its descendants do too.  That seemed
odd, because NAME doesn't appear in Windows' Environment Variables
dialog.  So I did a little hunting in the registry, and found
HKCU\Volatile Environment, which includes the NAME value.

I've never encountered HKCU\Volatile Environment before.  I believe
it's created by the Novell client when I log into our LAN.  Anyway,
clearing NAME from that key and relogging in solved the problem.
Thanks for the suggestion.

Andrew.


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