Skip to main content
Add links, inline link title , and rearrange
Source Link
bruno
  • 2.3k
  • 1
  • 19
  • 34

To steal @Baby 's answer from the comments and formalize it, this states that the 130 exit code is given by bashbash, and Mendel Cooper's Bash-Scripting Guide states that it indicates that the process was terminated by a SIGTERM. Generally this is the user pressing Ctrl-C.

To steal @Baby 's answer from the comments and formalize it, this states that the 130 exit code is given by bash, and indicates that the process was terminated by a SIGTERM. Generally this is the user pressing Ctrl-C.

To steal @Baby 's answer from the comments and formalize it, the 130 exit code is given by bash, and Mendel Cooper's Bash-Scripting Guide states that it indicates that the process was terminated by a SIGTERM. Generally this is the user pressing Ctrl-C.

added 29 characters in body
Source Link
Sinkingpoint
  • 7.7k
  • 2
  • 33
  • 46

To steal @Baby 's answer from the comments and formalize it, this states that the 130 exit code is given by bash, and indicates that the process was terminated by a SIGTERM. Generally this is the user pressing Ctrl-C.

To steal @Baby 's answer from the comments and formalize it, this states that the 130 exit code is given by bash, and indicates that the process was terminated by the user pressing Ctrl-C.

To steal @Baby 's answer from the comments and formalize it, this states that the 130 exit code is given by bash, and indicates that the process was terminated by a SIGTERM. Generally this is the user pressing Ctrl-C.

Source Link
Sinkingpoint
  • 7.7k
  • 2
  • 33
  • 46

To steal @Baby 's answer from the comments and formalize it, this states that the 130 exit code is given by bash, and indicates that the process was terminated by the user pressing Ctrl-C.