Current as of PowerShell [Core] 7.2.1 PowerShell-internal use of exit codes: PowerShell-internally, where native PowerShell commands generally run in-process, exit codes from child processes that run external programs play a very limited role: Native PowerShell commands generally don’t set exit codes and don’t act on them. PowerShell has an abstract counterpart to exit codes: $?, … Read more
Every command that runs has an exit status. That check is looking at the exit status of the command that finished most recently before that line runs. If you want your script to exit when that test returns true (the previous command failed) then you put exit 1 (or whatever) inside that if block after … Read more
You’re looking for calls to sys.exit() in the script. The argument to that method is returned to the environment as the exit code. It’s fairly likely that the script is never calling the exit method, and that 0 is the default exit code.
Three options: You can return it from Main if you declare your Main method to return int. You can call Environment.Exit(code). You can set the exit code using properties: Environment.ExitCode = -1;. This will be used if nothing else sets the return code or uses one of the other options above). Depending on your application … Read more
The standard doesn’t say. 0, EXIT_SUCCESS and EXIT_FAILURE have (sort of) specified meanings. Anything else depends on the implementation. At the present time, most Unix-based systems only support 8-bit return values. Windows supports (at least) a 32-bit return value. I haven’t checked whether 64-bit Windows supports a 64-bit return value, but I rather doubt it, … Read more
Using wait() or waitpid() It is not possible on Unix and derivatives using POSIX functions like wait() and waitpid(). The exit status information returned consists of two 8-bit fields, one containing the exit status, and the other containing information about the cause of death (0 implying orderly exit under program control, other values indicating that … Read more
Part 1: Advanced Bash Scripting Guide As always, the Advanced Bash Scripting Guide has great information: (This was linked in another answer, but to a non-canonical URL.) 1: Catchall for general errors 2: Misuse of shell builtins (according to Bash documentation) 126: Command invoked cannot execute 127: “command not found” 128: Invalid argument to exit … Read more
A pseudo environment variable named errorlevel stores the exit code: echo Exit Code is %errorlevel% Also, the if command has a special syntax: if errorlevel See if /? for details. Example @echo off my_nify_exe.exe if errorlevel 1 ( echo Failure Reason Given is %errorlevel% exit /b %errorlevel% ) Warning: If you set an environment variable … Read more