Site Tools


setenv
no way to compare when less than two revisions

Differences

This shows you the differences between two versions of the page.


setenv [2006/08/29 20:18] (current) – created - external edit 127.0.0.1
Line 1: Line 1:
 +#$EPIC: setenv.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $
 +======Synopsis:======
 +__setenv__ <var-name> <value> \\
 +__setenv__ -<var-name>
 +
 +======Description:======
 +In the first usage, __SETENV__ sets the environment variable <var-name>
 +to <value> This new value will be visible to all of the processes that
 +you [[exec command|EXEC]].  In the second usage, the environment
 +variable <var-name> is unset (deleted), and is no longer visible to
 +[[exec command|EXEC]] processes.
 +
 +Some systems (like Solaris) make changing and deleting environment 
 +variables painful.  Upon these kinds of systems, EPIC may output a 
 +warning advising you that setting an environment variable will result
 +in a memory leak which is unavoidable.  These systems also do not 
 +have an easy way to unset environment variables.  If you try, you will 
 +get a warning telling you this.
  
setenv.txt · Last modified: 2006/08/29 20:18 by 127.0.0.1