01-17-2007
In all shell scripts created? No.
Shell variables have significance only at runtime. If you run any of the scripts from your id, then the variable will be set. If you run it from any other id that does not set the variable, then the value will not be set.
Just because the variable value was set when the shell script was created does not mean that it will be set at runtime.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
what is the actual use of environment variables.
I know only PS1, LOGNAME, PS2 variables
what are the other variables & what is there use (2 Replies)
Discussion started by: indianguru
2 Replies
2. Programming
Hi!
How-to get the environment variables in GNU.
getenv() only fetches the ones that you can find under export (not the ones under declare)...
best regars .David (2 Replies)
Discussion started by: Esaia
2 Replies
3. UNIX for Dummies Questions & Answers
Hi Folks,
Is it possible somehow to unset all the environment variables which have been defined before in UNIX (Solaris).
Thanks,
Slava (3 Replies)
Discussion started by: spavlov
3 Replies
4. UNIX for Dummies Questions & Answers
hi,
1). i would like to know what is meant by environment variables?
2). is the number of envi variables is a constant number for unix systems?
3). how to see the list of envi variables (and the values of the envi variables)in a single command?
4). if this questions were already asked... (3 Replies)
Discussion started by: sekar sundaram
3 Replies
5. Programming
hi,
I want to create a new EV(Environment Variable) through a c program and I done this thing through setenv() method. But the newly created EV is not permanent, i.e. when I exit from the program the EV also no longer lives. But I want to make it a permanent EV for the current user. Actually I... (6 Replies)
Discussion started by: sumsin
6 Replies
6. UNIX for Dummies Questions & Answers
why are all environment variables represented in a fixed format regardless of the shell you use?
like $HOME $PATH etc (6 Replies)
Discussion started by: sravani
6 Replies
7. Shell Programming and Scripting
I have read tons of posts about how you can't set persisting environment variable in a child script of a shell and have it persist. The only way is to source a file as
% . <scriptname>
I am finding that true... but I know there is a way around it. I just don't know how. I worked for 6... (5 Replies)
Discussion started by: rwa25
5 Replies
8. HP-UX
Hi Experts,
Need your help in understanding the commands to setup the environment variables in hp-ux.
Beleive need to use either set,setenv or export.
I am confused between above three options, when to use which option?
On command line, I have tried both set and setenv but couldn't... (1 Reply)
Discussion started by: sai_2507
1 Replies
9. Homework & Coursework Questions
1. The problem statement:
What is the mesg value set for your environment? If it is on, how would you turn off your current
session? How would you set it permanently?
3. The attempts at a solution :
Read Unix The textbook.
3rd chapter has many things like environment variables and... (5 Replies)
Discussion started by: mahinkhan22
5 Replies
10. HP-UX
Hi All,
I need to understand following three environment variables and their usages in HP Unix.
_M_ARENA_OPTS
_M_CACHE_OPTS
PTHREAD_SCOPE_SYSTEM
How does these environment variables influence multi threaded applciation and how do we decide the value of these variables? Is there... (0 Replies)
Discussion started by: angshuman
0 Replies
LEARN ABOUT CENTOS
pcp.conf
PCP.CONF(5) File Formats Manual PCP.CONF(5)
NAME
pcp.conf - the Performance Co-Pilot configuration and environment file
SYNOPSIS
/etc/pcp.conf
DESCRIPTION
When using Performance Co-Pilot (PCP) tools and utilities and when calling PCP library functions, a standard set of environment variables
are defined in /etc/pcp.conf. These variables are generally used to specify the location of various PCP pieces in the file system and may
be loaded into shell scripts by sourcing the /etc/pcp.env(5) shell script and queried by C/C++ programs using the pmGetConfig(3) library
function. If a variable is already defined in the environment, the values in pcp.conf do not override those values, i.e. the values in
pcp.conf serve as installation defaults only.
Both the pcp.env and pcp.conf files are expected to be found in /etc by default. If required, the pcp.conf file may be relocated and
PCP_CONF set in the environment to specify the full path to the new location. The pcp.env file can not be relocated (this is the only hard
coded path required by PCP).
The syntax rules for pcp.conf are as follows :
1. the general syntax is
PCP_VARIABLE_NAME=variable value to end of line
2. lines that begin with # and all blank lines are ignored.
3. all variables must be prefixed with PCP_. This is a security issue - variables that do not have this prefix will be silently ignored.
4. there should be no space between the variable name and the literal = and no space between the = and the variable value (unless the
value actually starts with a space). This is required because the pcp.conf file may be sourced directly by Makefiles as well as inter-
preted by the pcp.env script and the pmGetConfig function.
5. variable values may contain spaces and should not be quoted. The pcp.env script automatically quotes all variable values from the
character immediately following the = through to the end of the line.
For further details and an explanation of the use of each variable, see the comments in the /etc/pcp.conf file itself.
ENVIRONMENT
The PCP_CONF environment variable specifies an alternative path to the pcp.conf file.
SEE ALSO
PCPIntro(1), PCPIntro(3), PMAPI(3), pmGetConfig(3) and pcp.env(5).
Performance Co-Pilot PCP PCP.CONF(5)