handling script/init errors
marc at cpdesign.com.au
Tue Nov 12 04:05:19 EST 2013
> > Is there a way to set up an error handler in the scripts? Ideally, a
> > command or script that could be called if /bin/sh encounters an error.
> What would you consider an error? Is executing the 'false' command an
> Commands in scripts must be allowed to fail. You are supposed to catch
> this via
> if [ $? != 0 ]; then
> echo "something bad happened"
> exit 1
"Error" is really a terrible, non-specific word. Sorry.
And to make it worse I'm not really sure what the error, um, problem, truly
I scattered a few "false" commands in the init script and it continued onto
the end, but when i added (on a board where there there is no bus #1):
# force reset audio dac in case audio playing during soft reset
i2c_write -b 1 -a 0x47 -r 0x55 0x80
This causes the init script to just stop and drop to a prompt, assuming
because bus #1 was not available. I haven't looked into how the errors/ return
codes are different.
> Of course error handling in shell is very cumbersome, even more in a
> restricted shell like hush. That's the reason I try to reduce the need
> of shell scripts in barebox. Most things that "really need to work" are
> better done in C.
I agree, especially "really need to work", (and that line above should have
really been in C) ..
Although, one of the things that I've really loved about barebox is that
ability to experiment and script with the shell, especially for basic testing.
> Maybe you could implement a 'catch' command. It would execute a command
> given as argument to the command. Something like:
> catch <command>
> Then whenever <command> fails $CATCH_HANDLER would be executed.
> Don't know if that makes sense, just an idea.
I was initially thinking of something like bash's "set +e" or "trap" but I
have neither good knowledge of how they work, or how they would/could be
implemented in bareox.
(Just vague, fading memories :) )
More information about the barebox