🧨 Bash: Execute Commands – Understanding exec and eval in Bash Scripts

Introduction to exec and eval in Bash – Dynamic and Direct Command Execution

Bash provides two advanced tools for executing commands: exec and eval. These commands serve very different purposes:

• exec replaces the current shell with another command.
• eval constructs and runs a command dynamically.

Understanding how to use them effectively helps you build dynamic, efficient, and secure Bash scripts for advanced automation, command construction, and performance tuning.

In this article, you’ll learn:

• How exec replaces the shell process
• How eval evaluates dynamic command strings
• Key differences and use cases
• Real-world examples for redirection, SSH, and command wrappers

What Does exec Do in Bash?

The exec command replaces the current shell process with the specified command. The shell doesn’t continue after exec; the new command takes over.

Example 1: Replace Shell with top

#!/bin/bash
exec top
echo "This will never run."

Output:

(top runs in place of the script — echo is never executed)

exec doesn’t spawn a new process. It replaces the shell itself.

Example 2: Redirect All Output to a Log File

#!/bin/bash
exec > output.log 2>&1
echo "This is logged to the file."

Creates output.log with:

This is logged to the file.

exec is also used to change file descriptors — very useful in logging or daemon scripts.

What Does eval Do in Bash?

The eval command evaluates a constructed command string and executes it as if it were typed at the shell.

Example 1: Construct and Run a Command

cmd="ls -l"
eval $cmd

Output:

(total and file listing)

Without eval, Bash would just treat $cmd as a string, not execute it.

Example 2: Dynamic Variable Expansion

varname="USER"
eval echo \$$varname

Output:

(your current username)

eval interprets \$USER and runs echo $USER.

Warning: eval Can Be Dangerous

Using eval on untrusted input is a major security risk. It executes arbitrary code, which can be exploited if input is manipulated.

Risky Example:

user_input='rm -rf /'
eval $user_input

🚨 This would run destructive commands if misused.

Summary Table – exec vs eval

Summary – Bash exec and eval

The exec and eval commands give you deep control over how scripts execute commands and manage process flows. Use exec for efficiency and resource control. Use eval for dynamic evaluation—but only with trusted input.

Key Takeaways:

• exec replaces the shell or redirects I/O
• eval builds and runs commands from strings
• exec is safer and used for logging or daemons
• eval is powerful but should be used with extreme care

Real-world Uses:

• exec to redirect output in logs or cron jobs
• eval to dynamically invoke commands in automation tools
• Use exec to launch programs from scripts without leaving background shells open

FAQ – Bash exec and eval

What happens after an exec command?
The current shell is replaced by the new command. Any code after exec does not run.

Is eval safe to use in Bash?
Only with fully trusted input. Avoid using eval with user data—it’s a common attack vector.

Can I use exec for logging all script output?
Yes:

exec > logfile.txt 2>&1

This redirects all future output in the script to the log file.

What’s a safe alternative to eval?
Use arrays or case statements instead of building commands as strings.

Can I use exec to run a script inside another script?
Yes. It replaces the parent script:

exec ./otherscript.sh