Tags

  • AWS (7)
  • Apigee (3)
  • ArchLinux (5)
  • Array (6)
  • Backtracking (6)
  • BinarySearch (6)
  • C++ (19)
  • CI&CD (3)
  • Calculus (2)
  • DesignPattern (43)
  • DisasterRecovery (1)
  • Docker (8)
  • DynamicProgramming (20)
  • FileSystem (11)
  • Frontend (2)
  • FunctionalProgramming (1)
  • GCP (1)
  • Gentoo (6)
  • Git (15)
  • Golang (1)
  • Graph (10)
  • GraphQL (1)
  • Hardware (1)
  • Hash (1)
  • Kafka (1)
  • LinkedList (13)
  • Linux (27)
  • Lodash (2)
  • MacOS (3)
  • Makefile (1)
  • Map (5)
  • MathHistory (1)
  • MySQL (21)
  • Neovim (10)
  • Network (66)
  • Nginx (6)
  • Node.js (33)
  • OpenGL (6)
  • PriorityQueue (1)
  • ProgrammingLanguage (9)
  • Python (10)
  • RealAnalysis (20)
  • Recursion (3)
  • Redis (1)
  • RegularExpression (1)
  • Ruby (19)
  • SQLite (1)
  • Sentry (3)
  • Set (4)
  • Shell (3)
  • SoftwareEngineering (12)
  • Sorting (2)
  • Stack (4)
  • String (2)
  • SystemDesign (13)
  • Terraform (2)
  • Tree (24)
  • Trie (2)
  • TwoPointers (16)
  • TypeScript (3)
  • Ubuntu (4)
  • Home

    set -o pipefail

    Published Feb 25, 2025 [  Shell  ]

    The set -o pipefail command is used in Bash scripts and interactive shells to change the behavior of pipelines.

    What does it do?

    When pipefail is enabled, a pipeline will return the exit status of the rightmost command that fails (i.e., exits with a non-zero status), rather than the exit status of the last command in the pipeline.

    Default Behavior (Without set -o pipefail):

    By default, a pipeline in Bash only returns the exit status of the last command.

    #!/bin/bash
    false | true
    echo $? # Output: 0 (Success, because 'true' is the last command)
    

    With set -o pipefail:

    When pipefail is set, the exit status of the pipeline is the first non-zero exit code in the pipeline (if any).

    #!/bin/bash
    set -o pipefail
    false | true
    echo $? # Output: 1 (Failure, because 'false' failed)
    

    Why is this useful?

    • Helps catch errors in pipelines that might otherwise go unnoticed.
    • Improves script robustness by ensuring failures propagate.
    • Useful in CI/CD pipelines or automation scripts where silent failures can be problematic.

    Example Use Case:

    set -o errexit # Exit script on any command failure
    set -o pipefail # Ensure pipeline failures are not ignored
    
    cat nonexistent.txt | grep "hello"
    
    # Without pipefail, the script might continue even if `cat` fails.