hi all ,
i wanted to know if someone knows how can i use
a variable inside another variable
e.g.
#!/bin/csh
foreach test(1 2 3)
set sta_$test = "2"
##now its the problem i want to echo the new var
#$sta_$test , each time with anothe num ($test = 1... (2 Replies)
I am using variable to give the location of the file I am using but I get error.
Here is the code:
LogFile=/tmp/log.email
echo -e "could not close the service - error number $error \n" > $LogFile
well this is not all the code but is enough because the problem start when I try to use the... (3 Replies)
Hi folks,
I am facing problem when I concat variables with the string.
Value for 'JDBC_CLASSES' variable looks malformed (/classes12.zip2.0KAGES)
But, my expected result for 'JDBC_CLASSES' is
/opt/API-R111/PACKAGES/jdbc/ORACLE9.2.0/classes12.zip
Am I missing anything here?
My... (10 Replies)
Hi all!
I know that environment variables can be set on the .bashrc file, but I need to set them from a sh script. I saw a lot of websites that teach this but it doesn't work for me.
#!/bin/sh
DEKTOP=$DESKTOP=:/home/rrodrigues/Desktop
export DESKTOP
if I do echo $DESKTOP returns me... (10 Replies)
can someone please explain to me what i'm doing wrong with this code:
WELT=$(awk '(($1 ~ "^${caag}$") || ($2 ~ "^${caag}$"))' /tmp/Compare.TEXT)
when run from the command line, it works. but it seems to be having a problem doing the comparison when variables are involved.
i tested from... (1 Reply)
hi,
i have a shell script which calls another shell which in turn calls another shell script.
Main_shell_script.sh
echo "In Main_shell_script.sh"
FILENAME="original.txt" # LINE 1
DST_FILENAME=$FILENAME # LINE 2
echo "FILENAME = {$FILENAME}"
echo "DST_FILENAME =... (3 Replies)
Hi All,
i have a requirement where i have to run a script with at least 25 arguements and position of arguements can also change. the unapropriate way is like below. can we achieve this in more good and precise way??
#!/bin/ksh
##script is sample.ksh
age=$1
gender=$2
class=$3
.
.
.... (3 Replies)
From the command line:
dions-air:scripts dion$ ls -l /Users/dion/Library/Application\ Support/Garmin/Devices/3816821036/History/2014-06-07-055251.TCX
-rw-r--r-- 1 dion staff 157934 7 Jun 06:55 /Users/dion/Library/Application Support/Garmin/Devices/3816821036/History/2014-06-07-055251.TCXworks... (2 Replies)
Discussion started by: dionbl
2 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)