07-06-2012
I think that is why we have "export" command!!
Please take a look into that!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Is there any way to pass variable to a sed script.For awk we have -v option.like that do we have any way to pass variable to a sed script from a awk script or from normal script?
Thanx,
sounder (1 Reply)
Discussion started by: sounder123
1 Replies
2. Shell Programming and Scripting
Im running a script that runs scripts within it self and i need to pass vars made in the original script to scripts run within it and the only way i can think to do it is right the string to a file and read the file in the script (4 Replies)
Discussion started by: rcunn87
4 Replies
3. Shell Programming and Scripting
I am new to scripting in AIX / UNIX. I have a script that runs 4 other scripts and I want to be able to pass in a agrument that I can check before I run the next script to see if the previous script finished with no errors.
Can someone send me an example of this as I'm sure it's pretty easy to... (1 Reply)
Discussion started by: David.Vilmain
1 Replies
4. UNIX for Dummies Questions & Answers
Hey all,
I'm wondering how you pass variable's that are defined in one script to another script that's been called by that first script.....
Best regards,
Jaz (1 Reply)
Discussion started by: Jazmania
1 Replies
5. Shell Programming and Scripting
Hi all.
I need to pass a value from a script that runs in a sub-shell, back into the calling shell like below (or into script 2 directly):
outer_script
export param=value1
script1 $param
(in script1: export param=value2)
script2 $param
($param is now value1, not value2... (4 Replies)
Discussion started by: bbergstrom74
4 Replies
6. Shell Programming and Scripting
Hi All,
I have two perl scripts say A.pl and B.pl.
A.pl interacts with Database and pulllls around 20 column-variables, which needs to be used in B.pl .
A.pl calls B.pl, I figured out that there exist a limit on number of arguments being passed as command line argument.
A.pl writing to a... (3 Replies)
Discussion started by: coolbhai
3 Replies
7. Shell Programming and Scripting
Hello everybody! First time posting here:)
Right, I am trying to pass arguments in my shell scripts using $1, $2 and $3 etc using if else statement........
This is my shell script which is based on serching the google website
#!/bin/sh
wget -t1 -E -e robots=off - -awGet.log -T 200 -H... (47 Replies)
Discussion started by: kev_1234
47 Replies
8. Shell Programming and Scripting
So this is something I've been wondering how to do for a while. Suppose I have two shell scripts a.sh and b.sh
script a does some function and outputs to a varable $x . I would then like to take $x into the second function, b.sh, and do a function on it and create some output. So how do you pass... (3 Replies)
Discussion started by: viored
3 Replies
9. Shell Programming and Scripting
Trying to do so
echo "111:222:333" |awk -F: '{system("export TESTO=" $2)}'But it doesn't work (2 Replies)
Discussion started by: urello
2 Replies
10. Shell Programming and Scripting
I have 2 scripts. test.sh, which calls submit2.sh. One of the parameters contains space and is quoted.
((((./submit2.sh Group_1_2_AMS_DAILY_CORE_GRP03 AMS AMS_D 'DAILY REPORT PROCEDURES'; echo $?>&3) | tee 1.log >&4)3>&1) | (read xs; exit $xs)) 4>&1
echo parm 1 = $1
echo parm 2 = $2... (1 Reply)
Discussion started by: andyclam
1 Replies
LEARN ABOUT CENTOS
devscripts.conf
DEVSCRIPTS.CONF(5) File Formats Manual DEVSCRIPTS.CONF(5)
NAME
devscripts.conf - configuration file for the devscripts package
DESCRIPTION
The devscripts package provides a collection of scripts which may be of use to Debian developers and others wishing to build Debian pack-
ages. Many of these have options which can be configured on a system-wide and per-user basis.
Every script in the devscripts package which makes use of values from these configuration files describes the specific settings recognised
in its own manpage. (For a list of the scripts, either see /usr/share/doc/devscripts/README.gz or look at the output of dpkg -L devscripts
| grep /usr/bin.)
The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings. They are written
with bash(1) syntax, but should only have comments and simple variable assignments in them; they are both sourced (if present) by many of
the devscripts scripts. Variables corresponding to simple switches should have one of the values yes and no; any other setting is regarded
as equivalent to the default setting.
All variable names are written in uppercase, and begin with the script name. Package-wide variables begin with "DEVSCRIPTS", and are
listed below, as well as in the relevant manpages.
For a list of all of the available options variables, along with their default settings, see the example configuration file
/usr/share/doc/devscripts/devscripts.conf.ex. This is copied to /etc/devscripts.conf when the devscripts package is first installed.
Information about configuration options introduced in newer versions of the package will be appended to /etc/devscripts.conf when the pack-
age is upgraded.
Every script which reads the configuration files can be forced to ignore them by using --no-conf as the first command-line option.
PACKAGE-WIDE VARIABLES
The currently recognised package-wide variables are:
DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
These variables control scripts which change directory to find a debian/changelog file or suchlike, and some other miscellaneous
cases. In order to prevent unwanted, even possibly dangerous, behaviour, these variables control when actions will be performed.
The scripts which currently make use of these variables are: debc, debchange/dch, debclean, debi, debrelease, debuild and uscan, but
this list may change with time (and I may not remember to update this manpage). Please see the manpages of individual scripts for
details of the specific behaviour for each script.
SEE ALSO
devscripts(1) and /usr/share/doc/devscripts/README.gz.
AUTHOR
This manpage was written for the devscripts package by the package maintainer Julian Gilbey <jdg@debian.org>.
DEBIAN
Debian Utilities DEVSCRIPTS.CONF(5)