Sponsored Content
Top Forums Shell Programming and Scripting Add Variable in .bash_profile Post 302524578 by mirni on Tuesday 24th of May 2011 01:28:33 AM
Old 05-24-2011
This sed command inserts (i) a line 'IMPACT_HOME=/my/new/path' before every line in infile; which is almost certainly not what you want.
You may want to make #1 look like:
Code:
grep -q IMPACT_HOME infile || sed '$ a IMPACT_HOME=/my/new/path' infile

which will append (a) the line at the end of file ($).

#2 is a little trickier. I think the intention was to substitute the definition of IMAPCT_HOME with a new path, however, this is a not quite well designed solution. The sed command there will replace any occurence of IMPACT_HOME until the end of line with 'IMPACT_HOME=/my/new/path'.
But what if infile contains some other statements containing IMPACT HOME, that are not a definition of it? E.g.:
Code:
if [ -z "$IMPACT_HOME" ] ; then 
 #do something
fi

would change into
Code:
if [ -z "$IMPACT_HOME=/my/new/path
 #do something
fi

and create syntax error(s).
I'd write #2 like this:
Code:
grep -q IMPACT_HOME infile && sed -i 's!^\([^#]*IMPACT_HOME=\)\(.*\)!\1/my/new/path #\2!' infile

Which will change the first line containing 'IMPACT_HOME='.
It will put the old definition (string after equal sign) into a comment on the same line. So, e.g. line:
Code:
IMPACT_HOME=/old/path

will become
Code:
IMPACT_HOME=/my/new/path #/old/path

It will only change (at most) one line (no 'g' at the end); and it will not change lines containing pound symbol before IMPACT_HOME (comments).

#1 and #2 can actually be put together into one (albeit long) line:
Code:
grep -q IMPACT_HOME infile && sed -i 's!^\([^#]*IMPACT_HOME=\)\(.*\)!\1/my/new/path #\2!' infile || sed '$ a IMPACT_HOME=/my/new/path' infile

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unrecognized Path in .bash_profile

Dear experts, I have installed Ruby in the following directory: $ pwd /home/ewijaya/.ruby $ ls bin lib share And I have also stated the PATH in my bash_profile like this: # .bash_profile # Get the aliases and functions if ; then . ~/.bashrc (1 Reply)
Discussion started by: monkfan
1 Replies

2. Shell Programming and Scripting

.bash_profile problem

Hi Guys, I modified my .bash_profile script , and tried to change the prompt. Following is the line of code in my .bash_profile script. export PS1=" \W " But I get the output as: \W This appears to be my prompt now. Any idea what should be done.. Thanks! (0 Replies)
Discussion started by: nua7
0 Replies

3. Shell Programming and Scripting

question in .bash_profile

We are more users using the oracle account, and people want to include theyr own files in .bash_profile. Like this: while ; do echo -n "LOGNAME is '$LOGNAME' (no sens), who are you? " >/dev/stderr read ln export LOGNAME=$ln done This works well when logging in to... (1 Reply)
Discussion started by: hannem
1 Replies

4. UNIX for Dummies Questions & Answers

bash_profile does not working

Hi all. when i connect as user megaguru i have a problem my .bash_profile does not working^:( if i do: . ./.bash_profile all enviroment variables are in place. How can i force linux to use .bash_profile before logon process? thanx in advance. (1 Reply)
Discussion started by: smallman
1 Replies

5. UNIX for Advanced & Expert Users

bash_profile or .profile

Hi, happy new year. on AIX 6.1 , for user oracle , there are two files : bash_profile and .profile I do not know which one is executed when login ? How to know , More over in both of them we have : in .profile : ORACLE_HOME=/appli/oracle/product/10.2.0/db_1... (5 Replies)
Discussion started by: big123456
5 Replies

6. Linux

How to add entry into .bash_profile file

Hi, Currently If i have created new userID then .bash_profile file is created under the new user. Now, I would like to add one path in this file. Please help on this . Current file output: # .bash_profile # Get the aliases and functions if ; then . ~/.bashrc fi #... (4 Replies)
Discussion started by: Mani_apr08
4 Replies

7. Shell Programming and Scripting

[Solved] How to increment and add variable length numbers to a variable in a loop?

Hi All, I have a file which has hundred of records with fixed number of fields. In each record there is set of 8 characters which represent the duration of that activity. I want to sum up the duration present in all the records for a report. The problem is the duration changes per record so I... (5 Replies)
Discussion started by: danish0909
5 Replies

8. Red Hat

.bash_profile file corrupted

Hi, Unexpectedly i entered wrong entries in .bash_profile for my user which has administrative permissions. So, i am getting errors for every command. I dont have backup file also, so any body can help me how to recover it. Regards, Mastan (7 Replies)
Discussion started by: mastansaheb
7 Replies

9. Shell Programming and Scripting

Is there a way to organize bash_profile across different platforms

I want to have one .bash_profile works on multiple platform, ubuntu, debian, redhat, cygwin, osx. So how should I organize .bash_profile? It can be multiple files in some subdir Let me brief you: what i want is a way to organize bash_profile across platforms so I can use one set of profiles... (2 Replies)
Discussion started by: John_Peter
2 Replies

10. UNIX for Dummies Questions & Answers

.bash_profile question

Hello everyone, I'm trying to set my .bash_profile to change my primary prompt from this: banbatchtest1v:MCPPRD:~>to this: banbatchtest1v:MCPPRD:/home/rcarvall> Here's what my .bash_profile looks like right now: # .bash_profile # Get the aliases and functions if ; then .... (2 Replies)
Discussion started by: galileo1
2 Replies
PMCPP(1)						      General Commands Manual							  PMCPP(1)

NAME
pmcpp - simple preprocessor for the Performance Co-Pilot SYNOPSIS
pmcpp [-D name[=value] ...] [infile] DESCRIPTION
pmcpp provides a very simple pre-processor for manipulating Performance Metric Name Space (PMNS) files for the Performance Co-Pilot (PCP). It is most commonly used internally to process the PMNS file(s) after pmLoadNameSpace(3) or pmLoadASCIINameSpace(3) is called. Input lines are read from infile (or standard input if infile is not specified), processed and written to standard output. All C-style comments of the form /* ... */ are stripped from the input stream. There are no predefined macros for pmcpp although macros may be defined on the command line using the -D option, where name and value must follow the same rules as described below for the #define directive. pmcpp accepts the following directives in the input stream (like cpp(1)): * #include "filename" or #include <filename> In either case the directory search path for filename tries filename first, then the directory for the command line infile (if any), followed by the $PCP_VAR_DIR/pmns directory. #include directives may be nested, up to a maximum depth of 5. * #define name value Defines a value for the macro name which must be a valid C-style name, so leading alphabetic or ``_'' followed by zero or more alphanu- merics or ``_''. value is optional (and defaults to an empty value) but when present it may not contain white space and quoting or escaping is not supported. * #undef name Removes the macro definition, if any, for name. * #ifdef name ... #endif or #ifndef name ... #endif The enclosing lines will be stripped or included, depending if the macro name is defined or not. Macro substitution is achieved by breaking the input stream into words separated by white space or one of the characters ``.'' or ``:'' - this matches the syntax of the PMNS, see pmns(5). Each word is checked and if it matches a macro name, the word is replaced by the macro value, otherwise the word is unchanged. There is generally one output line for each input line, although the line may be empty if the text has been stripped due to the handling of comments or conditional directives. When there is a change in the input stream, an additional output line is generated of the form: # line "name" to indicate the following line of output corresponds to line number line of the input file name. Important cpp(1) features that are not supported by pmcpp include: * #if expr ... #endif * Nested use of #ifdef or #ifndef. * #else within an #ifdef or #ifndef. * Stripping C++ style comments, as in // comment * Error recovery - the first error encountered by pmcpp will be fatal. * cpp(1) command line options like -U , -P and -I. PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura- tion file, as described in pcp.conf(5). SEE ALSO
cpp(1), pmLoadASCIINameSpace(3), pmLoadNameSpace(3), pmns(5), pcp.conf(5) and pcp.env(5). Performance Co-Pilot PMCPP(1)
All times are GMT -4. The time now is 05:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy