Working with Files and Directories

# CHAPTER 8

Working with Files and Directories #

1. Introduction #

2. Learning Objectives #

• Automate the creation of complex directory trees using mkdir -p.

• Utilize File Test Operators (-e, -d, -f) to safely verify environments before execution.

• Validate and modify file permissions dynamically from within a script.

• Automate file deletion and archiving operations safely.

• Architect a fail-safe, self-healing backup workflow.

3. Automated Directory Management #

#!/bin/sh
PROJECT_DIR="/var/data/project_alpha/logs"

echo "Provisioning directory structure..."
# -p ensures the script never crashes, even if the folder exists!
mkdir -p "$PROJECT_DIR"

4. Fail-Safe File Verification #

1. Verifying Files (-f):

#!/bin/sh
CONFIG="/etc/myapp/config.ini"

# Check if the file explicitly exists as a text file
if [ -f "$CONFIG" ]; then
    echo "Configuration found. Reading values..."
else
    echo "FATAL: Configuration missing at $CONFIG!"
    exit 1
fi

2. Verifying Directories (-d): Before you back up a database, ensure the target folder actually exists.

BACKUP_TARGET="/tmp/db_backups"

if [ -d "$BACKUP_TARGET" ]; then
    echo "Backup directory confirmed."
else
    echo "Directory missing! Attempting self-healing..."
    mkdir -p "$BACKUP_TARGET"
fi

*(Notice the architectural brilliance here: The script doesn't just crash and complain. It detects the missing folder and automatically builds it itself!)*

5. Managing Permissions Dynamically #

• -r : Checks for Read access.

• -w : Checks for Write access.

• -x : Checks for Execute access.

#!/bin/sh
LOG_FILE="/var/log/syslog"

# Check if we have write permission
if [ -w "$LOG_FILE" ]; then
    echo "Server booted successfully." >> "$LOG_FILE"
else
    echo "ERROR: Write permission denied. Did you run with sudo?"
fi

6. Safe File Deletion #

• Always quote the variable: rm -f "$FILE" (Prevents word-splitting disasters).

• Always verify the file exists before deleting, or use -f to force silent deletion without throwing an error if it's missing.

7. Diagrams/Visual Suggestions #

• Path True (Yes): Arrow goes straight down to Node 4: Copy files.

• Path False (No): Arrow loops out to a side box (Node 3): mkdir -p /backups, and then an arrow flows back into Node 4: Copy files.

8. Best Practices #

• Absolute Paths for Cron: If your script interacts with files (like cp file.txt /tmp), it might work perfectly when you run it interactively. But if you schedule it via cron, it will fail. Why? Because cron runs in a different working directory. Always use Absolute Paths (cp /home/user/file.txt /tmp) in automation scripts.

9. Common Mistakes #

• Confusing -e and -f: Beginners often use the -e (Exists) operator to check for a configuration file. This is dangerous. If a user accidentally created a *Directory* with that exact name, -e will return True, your script will attempt to read the directory as a text file, and it will crash. Always use -f (Regular File) when you explicitly expect text data.

10. Mini Project: The Self-Healing Backup Workflow #

1. 1. nano archive_logs.sh

1. 2. Write the code:

#!/bin/sh

SOURCE_FILE="/var/log/syslog"
DEST_DIR="/archive/logs"
TIMESTAMP=$(date +"%Y%m%d")

echo "--- INITIATING SECURE ARCHIVAL ---"

# 1. Verify Source
if [ ! -f "$SOURCE_FILE" ]; then
    echo "FATAL: Source log file does not exist. Aborting."
    exit 1
fi

# 2. Verify Permissions
if [ ! -r "$SOURCE_FILE" ]; then
    echo "FATAL: Read permission denied on source file. Run as root."
    exit 1
fi

# 3. Verify Destination & Self-Heal
if [ ! -d "$DEST_DIR" ]; then
    echo "Destination directory missing. Rebuilding path $DEST_DIR..."
    # Suppress errors if permission denied, handle carefully in real prod
    mkdir -p "$DEST_DIR"
fi

# 4. Execute the action securely
TARGET_ARCHIVE="$DEST_DIR/syslog_backup_$TIMESTAMP.cp"
echo "Copying data to $TARGET_ARCHIVE..."
cp "$SOURCE_FILE" "$TARGET_ARCHIVE"

echo "Archival process completed successfully."

1. 3. This is a production-grade script. It anticipates failure at every step and handles it gracefully.

11. Practice Exercises #

1. 1. Explain the operational difference between the -e, -f, and -d File Test operators. Provide a specific scenario where using -e instead of -d would result in a catastrophic script failure.

1. 2. Detail the exact mechanical behavior of the mkdir -p command. Why is the -p flag considered an absolute necessity when writing automated provisioning scripts?

12. MCQs with Answers #

13. Interview Questions #

• Q: A junior engineer writes a deployment script containing the command cp /config/settings.ini /backups/settings.ini. The script crashes on brand-new servers because the /backups directory hasn't been created yet. Walk me through the exact conditional logic (using -d and mkdir -p) you would inject into the script to make it autonomously self-healing.

• Q: Explain the necessity of explicitly wrapping file path variables in double quotes within test brackets (e.g., [ -f "$FILE_PATH" ]). What specific vulnerability does this prevent regarding Unix file naming conventions?

• Q: Contrast the -f operator with the -x operator in shell scripting. In what specific administrative scenario would you utilize the -x operator before executing a command?

14. FAQs #

15. Summary #

16. Next Chapter Recommendation #