Why export command in Linux CLI? - Purpose & Use Cases

The Big Idea

What if a simple command could save you from repeating the same setup over and over?

The Scenario

Imagine you open a terminal and set a variable like MYVAR=hello. Then you run a program or script that needs to use MYVAR. But the program says it can't find it. You try to set it again inside the program, but it doesn't work as expected.

The Problem

Manually setting variables inside each program or script is slow and frustrating. You have to repeat the same setup every time. Also, if you forget to share the variable properly, your programs won't see it, causing errors and wasted time.

The Solution

The export command solves this by marking variables to be shared with all child programs and scripts. Once you export a variable, every program you run from that terminal can use it automatically, saving you from repeating work and avoiding mistakes.

Before vs After

✗ Before

MYVAR=hello
./my_script.sh  # script can't see MYVAR

✓ After

export MYVAR=hello
./my_script.sh  # script can use MYVAR

What It Enables

With export, you can easily share important settings and data across all your programs and scripts, making your work smoother and faster.

Real Life Example

Suppose you set a database password as an environment variable. By exporting it, any script or tool you run can access the password without you typing it again and again, keeping your workflow secure and efficient.

Key Takeaways

Manually passing variables to programs is repetitive and error-prone.

export shares variables with all child processes automatically.

This makes scripts and programs work together smoothly without extra setup.

Practice

1. What does the export command do in a Linux shell?

easy

A. Makes a shell variable available to child processes

B. Deletes a shell variable permanently

C. Lists all files in the current directory

D. Changes the current directory

Solution

1. Step 1: Understand shell variables and environment

   Shell variables exist only in the current shell session unless exported.

2. Step 2: Role of export

   The export command marks a variable to be passed to child processes as environment variables.

3. Final Answer:

   Makes a shell variable available to child processes -> Option A

4. Quick Check:

   export = share variable with child processes [OK]

Hint: Export shares variables with child processes [OK]

Common Mistakes:

• Thinking export deletes variables
• Confusing export with file commands
• Assuming export changes directories

2. Which of the following is the correct syntax to export a variable named PATH with value /usr/local/bin?

easy

A. export =PATH /usr/local/bin

B. export PATH=/usr/local/bin

C. export PATH : /usr/local/bin

D. export PATH == /usr/local/bin

Solution

1. Step 1: Recall export syntax

   The correct syntax is export VARIABLE=VALUE without spaces around the equal sign.

2. Step 2: Check each option

   export PATH=/usr/local/bin matches the correct syntax. Others have invalid characters or spaces.

3. Final Answer:

   export PATH=/usr/local/bin -> Option B

4. Quick Check:

   export VAR=VALUE no spaces [OK]

Hint: No spaces around = in export syntax [OK]

Common Mistakes:

• Adding spaces around equal sign
• Using wrong symbols like : or ==
• Placing export after assignment

3. What will be the output of the following commands?

MYVAR="hello"
echo $MYVAR
export MYVAR
bash -c 'echo $MYVAR'

medium

A. \n\n

B. hello\n

C. \nhello

D. hello\nhello

Solution

1. Step 1: Understand variable assignment and export

   First, MYVAR is set to "hello" and printed, so first echo outputs "hello". Then MYVAR is exported.

2. Step 2: Child shell access

   The bash -c 'echo $MYVAR' runs a new shell which inherits exported variables, so it prints "hello" again.

3. Final Answer:

   hello hello -> Option D

4. Quick Check:

   Exported variable visible in child shell [OK]

Hint: Exported vars visible in child shells [OK]

Common Mistakes:

• Assuming unexported vars appear in child shells
• Confusing echo outputs with command prompts
• Ignoring export effect on subshells

4. Identify the error in this script snippet:

export MYVAR
MYVAR="world"
echo $MYVAR

medium

A. echo command is missing quotes

B. export command syntax is wrong

C. MYVAR is exported before assignment, so child shells get empty value

D. No error, script works fine

Solution

1. Step 1: Analyze export before assignment

   Exporting MYVAR before assigning means MYVAR is empty when exported.

2. Step 2: Effect on variable value

   Assigning MYVAR after export does not update the exported environment variable for child processes.

3. Final Answer:

   MYVAR is exported before assignment, so child shells get empty value -> Option C

4. Quick Check:

   Export before assignment exports empty value [OK]

Hint: Assign before export to share correct value [OK]

Common Mistakes:

• Exporting before assigning value
• Thinking export syntax is wrong
• Assuming echo needs quotes always

5. You want to set a variable CONFIG_PATH to /etc/config and ensure it is available to all scripts run from your current shell session and its children. Which sequence of commands achieves this correctly?

hard

A. CONFIG_PATH=/etc/config\nexport CONFIG_PATH

B. export CONFIG_PATH=/etc/config

C. export CONFIG_PATH\nCONFIG_PATH=/etc/config

D. CONFIG_PATH=/etc/config

Solution

1. Step 1: Assign variable before export

   Assigning CONFIG_PATH=/etc/config sets the value in the current shell.

2. Step 2: Export variable after assignment

   Running export CONFIG_PATH marks it for child processes with the assigned value.

3. Step 3: Check other options

   export CONFIG_PATH=/etc/config works but is less clear; export CONFIG_PATH\nCONFIG_PATH=/etc/config exports before assignment (wrong); CONFIG_PATH=/etc/config does not export.

4. Final Answer:

   CONFIG_PATH=/etc/config export CONFIG_PATH -> Option A

5. Quick Check:

   Assign then export to share variable [OK]

Hint: Assign first, then export to share variable [OK]

Common Mistakes:

• Exporting before assigning value
• Not exporting variable at all
• Assuming single export with assignment is always best