I have this in a bash script:

exit 3;

exit_code="$?"

if [[ "$exit_code" != "0" ]]; then
    echo -e "${r2g_magenta}Your r2g process is exiting with code $exit_code.${r2g_no_color}";
    exit "$exit_code";
fi

It looks like it will exit right after the exit command, which makes sense. I was wondering is there some simple command that can provide an exit code without exiting right away?

I was going to guess:

exec exit 3

but it gives an error message: exec: exit: not found.  What can I do? :)

New contributor
MrCholo is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
  • 1
    Yeah exec exit 3 is no bueno, I get "exec: exit: not found" – MrCholo 14 hours ago
  • I don't understand the question. Why not set exit_code=3 and eliminate the exit 3 line altogether? – wjandrea 4 hours ago
up vote 19 down vote accepted

If you have a script that runs some program and looks at the program's exit status (with $?), and you want to test that script by doing something that causes $? to be set to some known value (e.g., 3), just do

(exit 3)

The parentheses create a sub-shell.  Then the exit command causes that sub-shell to exit with the specified exit status.

exit is a bash built-in, so you can't exec it. Per bash's manual:

Bash's exit status is the exit status of the last command executed in the script. If no commands are executed, the exit status is 0.

Putting all this together, I'd say your only option is to store your desired exit status in a variable and then exit $MY_EXIT_STATUS when appropriate.

New contributor
solarshado is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
  • hmmm what do you think about @G-man's idea? – MrCholo 13 hours ago
  • 1
    Maybe I misunderstood what you're trying to accomplish. If you're just trying to set $? (though I'm not really sure why you would), that does seem like a solid answer. If you just want to set it to some unsuccessful value, false is another option. – solarshado 13 hours ago

You can write a function that returns the status given as argument, or 255 if none given. (I call it ret as it "returns" its value.)

ret() { return "${1:-255}"; }

and use ret in place of your call to exit. This is avoids the inefficiency of creating the sub-shell in the currently accepted answer.

  • 2
    @iBug The extra space is not needed. – icarus 9 hours ago
  • Good point about the inefficiency of creating the sub-shell.  I've read that some shells might be smart enough to optimize the fork out in cases like this, but that bash isn't one of them. – G-Man 3 hours ago

About exec exit 3... it would try to run an external command called exit, but there isn't one, so you get the error. It has to be an external command instead of one built in to the shell, since exec replaces the shell completely. Which also means that even if you had an external command called exit, exec exit 3 would not return to continue your shell script, since the shell wouldn't be there any more.

  • I guess you could do exec bash -c "exit 3", but at the moment I can't think of any reason to do that as opposed to just exit 3. – David Z 6 hours ago
  • @DavidZ, in any case, exec'ing or just exit'ing will stop the script, which didn't seem like what the question wanted. – ilkkachu 5 hours ago

You can do this with Awk:

awk 'BEGIN{exit 9}'

Or Sed:

sed Q9 /proc/stat
  • ...or with a shell: sh -c 'exit 9' – ilkkachu 5 hours ago
  • @ilkkachu if youre going to do that you might as well do the (exit 9) in the accepted answer – Steven Penny 3 hours ago

Your Answer

MrCholo is a new contributor. Be nice, and check out our Code of Conduct.

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.