03-24-2010
The difference is this: if you run a script, then any values defined there are visible only to that process, and maybe their subprocesses if you export them. If, on the other hand, you source them (using either 'source' or the more portable '.' syntax) the file will be executed in the current shells context, thus making the exported variables available in the current shell.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there any difference between these 2 commands :-
export var="a"
and
var="a"
export var (2 Replies)
Discussion started by: radhika03
2 Replies
2. Shell Programming and Scripting
Me dumb. Can't get this to work...
#!/bin/sh
export JAVA_HOME_BAK=${JAVA_HOME}
or
#!/bin/sh
export JAVA_HOME_BAK=/usr/java
or
#!/bin/sh
export JAVA_HOME_BAK=$JAVA_HOME
or
#!/bin/sh
export JAVA_HOME_BAK $JAVA_HOME
etc.... none work.
Either i get: "JAVA_HOME_BAK=/usr/java: is not... (1 Reply)
Discussion started by: xplodersuv
1 Replies
3. UNIX for Dummies Questions & Answers
hi, :)
I created a main script called "Paymain.prg" ( /proj/paymain.prg)
In this script i created two variables as follows
MASTER=/HOME/emaster.dbf
TRAN=/HOME/etran.dbf
Aftre that i exported that two variables
EXPORT MASTER TRAN
But when i use these two variable in another script calld... (3 Replies)
Discussion started by: ravi raj kumar
3 Replies
4. Solaris
Hi Guys,
Thanks for taking the time to read the problem i having outlined below:
Before i go into the problem can you please tell me what the following means?
a. "dt" stands for and what does it means?
Configuration Below:
1x Unix Server
2x Unix Terminals
(both systems are... (3 Replies)
Discussion started by: tlee
3 Replies
5. Shell Programming and Scripting
Sorry for the duplicate thread this one is similar to the one in
https://www.unix.com/shell-programming-scripting/88132-awk-sed-script-read-values-parameter-files.html#post302255121
Since there were no responses on the parent thread since it got resolved partially i thought to open the new... (4 Replies)
Discussion started by: rajan_san
4 Replies
6. Shell Programming and Scripting
Hello All,
I am transferring a file from one server to another server.
File name is stored as Wip_DD-MM-YY .i.e if we run the program today the file is stored as Wip_18-FEB-09.txt.
This file i need to transfer.
My question is how do we assign the this filename to a variable.
i treid in... (3 Replies)
Discussion started by: chpraveen_862
3 Replies
7. Shell Programming and Scripting
Hi, I am facing a problem while scheduling an export of a table using cron job. I have written a simple export command inside a shell script test.sh like
echo started
exp schemaname/temp1234 file= /test/d.dmp tables=per_st log= /test/d.log
echo ended
I tried scheduling it through... (6 Replies)
Discussion started by: beautifulmind
6 Replies
8. Shell Programming and Scripting
I have a txt file from which i am assiging a value to a variable
using the code in script1
script1.sh
export f=$(sed -n "/Freq *=/ s/.*= *//p" ${R_path}/output.txt)
echo "$f" --------> this works
in script2 ( which executes the script1)
eval ./script1.sh
if && ; then
echo... (1 Reply)
Discussion started by: shashi792
1 Replies
9. Shell Programming and Scripting
I am running the export command within a view to use that value inside my build script. But while executing it it is saying "export command not found"
My code is as follows:
--------------------------
#!/bin/sh
user="test"
DIR="/bldtmp/"$user
VIEW="test.view1"
echo "TMPDIR before export... (4 Replies)
Discussion started by: dchoudhury
4 Replies
10. Shell Programming and Scripting
i am beginner in shell scripting.
not able to understand what below line will do.
PS1=${HOST:=Žuname -nŽ}"$ " ; export PS1 HOST
below is the script
#!/bin/hash
PS1=${HOST:=Žuname -nŽ}"$ " ; export PS1 HOST ;
echo $PS1
and i getting the below output
Žuname -nŽ$ (25 Replies)
Discussion started by: scriptor
25 Replies
EXPORT(P) POSIX Programmer's Manual EXPORT(P)
NAME
export - set the export attribute for variables
SYNOPSIS
export name[=word]...
export -p
DESCRIPTION
The shell shall give the export attribute to the variables corresponding to the specified names, which shall cause them to be in the envi-
ronment of subsequently executed commands. If the name of a variable is followed by = word, then the value of that variable shall be set to
word.
The export special built-in shall support the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.
When -p is specified, export shall write to the standard output the names and values of all exported variables, in the following format:
"export %s=%s
", <name>, <value>
if name is set, and:
"export %s
", <name>
if name is unset.
The shell shall format the output, including the proper use of quoting, so that it is suitable for reinput to the shell as commands that
achieve the same exporting results, except:
1. Read-only variables with values cannot be reset.
2. Variables that were unset at the time they were output need not be reset to the unset state if a value is assigned to the variable
between the time the state was saved and the time at which the saved output is reinput to the shell.
When no arguments are given, the results are unspecified.
OPTIONS
See the DESCRIPTION.
OPERANDS
See the DESCRIPTION.
STDIN
Not used.
INPUT FILES
None.
ENVIRONMENT VARIABLES
None.
ASYNCHRONOUS EVENTS
Default.
STDOUT
See the DESCRIPTION.
STDERR
The standard error shall be used only for diagnostic messages.
OUTPUT FILES
None.
EXTENDED DESCRIPTION
None.
EXIT STATUS
Zero.
CONSEQUENCES OF ERRORS
Default.
The following sections are informative.
APPLICATION USAGE
None.
EXAMPLES
Export PWD and HOME variables:
export PWD HOME
Set and export the PATH variable:
export PATH=/local/bin:$PATH
Save and restore all exported variables:
export -p > temp-fileunset a lot of variables... processing. temp-file
RATIONALE
Some historical shells use the no-argument case as the functional equivalent of what is required here with -p. This feature was left
unspecified because it is not historical practice in all shells, and some scripts may rely on the now-unspecified results on their imple-
mentations. Attempts to specify the -p output as the default case were unsuccessful in achieving consensus. The -p option was added to
allow portable access to the values that can be saved and then later restored using; for example, a dot script.
FUTURE DIRECTIONS
None.
SEE ALSO
Special Built-In Utilities
COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol-
ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE
and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained
online at http://www.opengroup.org/unix/online.html .
IEEE
/The Open Group 2003 EXPORT(P)