Pass all variables from one shell script to another?

by

You have basically two options:

  1. Make the variable an environment variable (export TESTVARIABLE) before executing the 2nd script.
  2. Source the 2nd script, i.e. . test2.sh and it will run in the same shell. This would let you share more complex variables like arrays easily, but also means that the other script could modify variables in the source shell.

UPDATE:

To use export to set an environment variable, you can either use an existing variable:

A=10
# ...
export A

This ought to work in both bash and sh. bash also allows it to be combined like so:

export A=10

This also works in my sh (which happens to be bash, you can use echo $SHELL to check). But I don’t believe that that’s guaranteed to work in all sh, so best to play it safe and separate them.

Any variable you export in this way will be visible in scripts you execute, for example:

a.sh:

#!/bin/sh

MESSAGE="hello"
export MESSAGE
./b.sh

b.sh:

#!/bin/sh

echo "The message is: $MESSAGE"

Then:

$ ./a.sh
The message is: hello

The fact that these are both shell scripts is also just incidental. Environment variables can be passed to any process you execute, for example if we used python instead it might look like:

a.sh:

#!/bin/sh

MESSAGE="hello"
export MESSAGE
./b.py

b.py:

#!/usr/bin/python

import os

print 'The message is:', os.environ['MESSAGE']

Sourcing:

Instead we could source like this:

a.sh:

#!/bin/sh

MESSAGE="hello"

. ./b.sh

b.sh:

#!/bin/sh

echo "The message is: $MESSAGE"

Then:

$ ./a.sh
The message is: hello

This more or less “imports” the contents of b.sh directly and executes it in the same shell. Notice that we didn’t have to export the variable to access it. This implicitly shares all the variables you have, as well as allows the other script to add/delete/modify variables in the shell. Of course, in this model both your scripts should be the same language (sh or bash). To give an example how we could pass messages back and forth:

a.sh:

#!/bin/sh

MESSAGE="hello"

. ./b.sh

echo "[A] The message is: $MESSAGE"

b.sh:

#!/bin/sh

echo "[B] The message is: $MESSAGE"

MESSAGE="goodbye"

Then:

$ ./a.sh
[B] The message is: hello
[A] The message is: goodbye

This works equally well in bash. It also makes it easy to share more complex data which you could not express as an environment variable (at least without some heavy lifting on your part), like arrays or associative arrays.

More Related Contents:

  1. How to concatenate string variables in Bash
  2. Are shell scripts sensitive to encoding and line endings?
  3. How do I use shell variables in an awk script?
  4. Difference between sh and Bash
  5. How can I debug a Bash script? [closed]
  6. Pass commands as input to another command (su, ssh, sh, etc)
  7. Why do you need ./ (dot-slash) before executable or script name to run it in bash?
  8. How can I repeat a character in Bash?
  9. How can I declare and use Boolean variables in a shell script?
  10. Test for non-zero length string in Bash: [ -n “$var” ] or [ “$var” ]
  11. Automatic exit from Bash shell script on error [duplicate]
  12. Ubuntu says “bash: ./program Permission denied” [closed]
  13. Using the RUN instruction in a Dockerfile with ‘source’ does not work
  14. Is there a TRY CATCH command in Bash
  15. Set a parent shell’s variable from a subshell
  16. Value too great for base (error token is “08”) [duplicate]
  17. What expands to all files in current directory recursively?
  18. find: missing argument to -exec
  19. Looping through all files in a directory [duplicate]
  20. Is mixing getopts with positional parameters possible?
  21. Connect to sqlplus in a shell script and run SQL scripts
  22. How to resolve symbolic links in a shell script
  23. Convert seconds to hours, minutes, seconds
  24. How to check if running as root in a bash script
  25. Print a file’s last modified date in Bash
  26. Temporarily change current working directory in bash to run a command [duplicate]
  27. How to break out of a loop in Bash?
  28. How to tell if a string is not defined in a Bash shell script
  29. BASH: Writing a Script to Recursively Travel a Directory of N Levels
  30. How to grep for case insensitive string in a file?

Leave a Comment