Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Thu, 20 Feb 2003 11:50:45 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Fred Ma <fma AT doe DOT carleton DOT ca>
cc: cygwin AT cygwin DOT com
Subject: Re: Question re. export environment variable
In-Reply-To: <3E550005.84B691EA@doe.carleton.ca>
Message-ID: <Pine.GSO.4.44.0302201142550.16682-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 20 Feb 2003, Fred Ma wrote:

> Hello,
>
> I'm using cygwin bash 2.05b-8 (it's actually gnu).
> I thought that $HOSTNAME was an environment
> variable.  When I run gnu make (I'm pretty
> sure this is not a make problem), $(HOSTNAME)
> is empty.  It gets fixed if I do "export HOSTNAME"
> before running make.
>
> Is there a way to check if the export command
> has been applied to $HOSTNAME?  Does the
> actual transcription of $HOSTNAME's value to
> the environment happen only once, when
> "export" is applied, or is there a continual
> monitoring an mirroring of changes to $HOSTNAME
> forever after applying "export"?
>
> Fred

Fred,

I'm afraid you might be confused about what "exporting" a variable means.
Bash maintains an "environment", which contains the values of all the
variables it's using.  When bash spawns a child, that child inherits those
variables from the parent's environment that are "exported".  Thus, if you
export HOSTNAME, the child will get the current value of HOSTNAME.  If you
then change HOSTNAME in the parent, the child *will not* see the change.
However, if you spawn another child, that new child *will* see the new
value.

BTW, "export" with no variable name will print out the list of all
variables that are exported from the current shell.  And, if you want to
make sure it's exported, "export HOSTNAME" can do no harm.  But both this
and the above are off-topic for the Cygwin list, and could have been found
by a simple perusal of "man bash".
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/