📘 Command Grouping

---

🎯 What You Will Learn

1. Understand the concept of command grouping in Bash scripting.
2. Learn how to execute multiple commands as a single unit using {} and ().
3. Differentiate between current shell grouping and subshell grouping.
4. Apply grouping in practical WordPress and VPS automation tasks.
5. Learn to use grouping for redirection, conditional execution, and performance efficiency.
6. Identify common mistakes when using curly braces and parentheses.

---

1. 5W + 1H Framework

Element	Description
What	Command grouping allows multiple commands to be treated as a single command block.
Why	Enables logical structuring, combined redirection, and isolated execution.
Who	System administrators, DevOps engineers, and WordPress VPS managers automating multiple tasks.
Where	Inside Bash scripts or directly in the Linux shell.
When	When you need to execute multiple commands conditionally, sequentially, or within a subshell.
How	Use { command1; command2; } for the same shell, or ( command1; command2 ) for a subshell.

---

2. Prerequisites

• Basic knowledge of Bash syntax and file permissions.
• Understanding of redirection (>, >>) and piping (|).
• Ability to run and test Bash scripts (chmod +x script.sh).
• Familiarity with terminal navigation commands (cd, ls, etc.).

---

3. Core Structure: {} vs () Grouping

Symbol	Name	Execution Context	Scope	Variable Visibility	Use Case
{ }	Brace Group	Same shell	Shared	Shares variables	Configuration blocks, logical grouping
( )	Subshell Group	New shell	Isolated	Does not share variables	Background tasks, testing, isolation

---

4. Syntax Examples and Expected Output

4.1 Using {} – Current Shell Group

{ echo "Backing up WordPress site..."; tar -czf /home/backup/wp.tar.gz /var/www/html; echo "Backup complete."; }

Expected Output:

Backing up WordPress site...
Backup complete.

Explanation: All commands inside {} run in the same shell. Variables defined before the block remain available after execution.

4.2 Using () – Subshell Group

( cd /var/www/html && ls && echo "Listing done inside subshell." )

Expected Output:

index.php
wp-config.php
wp-content
Listing done inside subshell.

After this, the working directory returns to the parent shell. cd /var/www/html inside the parentheses doesn’t affect your main shell’s directory.

4.3 Difference in Variable Scope

var="Hello"
{ var="Changed in brace"; }
echo $var

Expected Output:

Changed in brace

Now with parentheses:

var="Hello"
( var="Changed in subshell" )
echo $var

Expected Output:

Hello

Explanation: {} shares variables with the parent shell. (), being a subshell, does not affect parent variables.

5. Combining with Redirection

5.1 Redirect Output of Multiple Commands Together

{ echo "Starting backup"; tar -czf /home/backup/site.tar.gz /var/www/html; echo "Backup done"; } > /var/log/backup.log 2>&1

Expected Output (in terminal):

# No terminal output

Expected Log (/var/log/backup.log):

Starting backup
Backup done

Benefit: one redirection applies to all commands in the group.

6. Combining with Conditional Logic

6.1 Using && and ||

{ systemctl restart lsws && echo "Web server restarted"; } || echo "Restart failed"

Expected Output (if success):

Web server restarted

Expected Output (if fail):

Restart failed

This ensures graceful fallback if a grouped operation fails.

7. Real Use Cases in WordPress VPS

Use Case	Example	Description
Backup & Cleanup	{ tar -czf wp.tar.gz /var/www/html; rm -rf /tmp/cache; }	Executes backup and cleanup together.
Update Workflow	( cd /var/www/html && wp plugin update --all && wp theme update --all )	Runs updates in a safe isolated subshell.
Error Logging	{ wp db export db.sql; wp option update maintenance_mode 0; } >> /var/log/wp_maint.log 2>&1	Group logs into a single output file.
Conditional Reload	`{ systemctl reload lsws && echo "Reloaded"; }

---

8. Subshells in Parallel Execution

You can run subshells in the background to parallelize tasks.

( tar -czf backup1.tar.gz /var/www/site1 ) &
( tar -czf backup2.tar.gz /var/www/site2 ) &
wait
echo "Both backups finished."

Expected Output:

Both backups finished.

Explanation: The & operator runs each subshell in parallel, and wait ensures all are completed before continuing.

9. Static vs Dynamic Framing

Aspect	Static Grouping {}	Dynamic Grouping ()
Shell Context	Same shell	New shell
Variable Sharing	Yes	No
Performance	Slightly faster	Slight overhead
Isolation	No	Yes
Best Use Case	Sequential related commands	Temporary environment (cd, test, parallel)

---

10. Troubleshooting Matrix

Issue	Cause	Fix
“syntax error near unexpected token”	Missing semicolon or space before }	Ensure each command ends with ; and a space before }
Group redirection fails	Using > before {}	Place > after the block
Variable not retained	Using () instead of {}	Use {} to stay in same shell
Subshell command not found	Missing PATH variables in cron	Use absolute paths for commands

---

11. Quick Lab – Grouped Backup Script

Script: group_backup.sh

#!/bin/bash
BACKUP_DIR="/home/backup"
LOG="/var/log/wp_group_backup.log"

{
  echo "Starting WordPress backup at $(date)";
  tar -czf "$BACKUP_DIR/wp_backup_$(date +%F_%H%M).tar.gz" /var/www/html;
  echo "Backup complete for $(hostname)";
} >> "$LOG" 2>&1

Run:

chmod +x group_backup.sh
./group_backup.sh

Expected Output (in /var/log/wp_group_backup.log):

Starting WordPress backup at 2025-10-06 14:21
Backup complete for vps-01

---

12. Cheat Sheet

Task	Command / Syntax
Group commands in same shell	{ cmd1; cmd2; }
Group commands in subshell	( cmd1; cmd2 )
Redirect output for group	{ cmd1; cmd2; } > file.log 2>&1
Run groups in parallel	( cmd1 ) & ( cmd2 ) & wait
Conditional grouping	`{ cmd1 && cmd2; }
Test variable persistence	{ var=1; } && echo $var → retained
Subshell test	( var=1; ) && echo $var → empty

---

13. Mini-Quiz

#	Question	Answer
1	What symbol is used for same-shell grouping?	{ }
2	What symbol creates a subshell grouping?	( )
3	What happens to variables inside ( )?	They are not visible outside.
4	How do you apply one redirection to all grouped commands?	Use { cmd1; cmd2; } > output.log
5	Why might you use subshell grouping for WordPress updates?	It isolates directory changes and prevents path contamination.

---

---