bash "set -e"
set -e causes the shell to exit if any subcommand or pipeline returns a non-zero status.
The answer the interviewer was probably looking for is:
It would be dangerous to use "set -e" when creating init.d scripts:
From http://www.debian.org/doc/debian-policy/ch-opersys.html 9.3.2 --
Be careful of using set -e in init.d scripts. Writing correct init.d scripts requires accepting various error exit statuses when daemons are already running or already stopped without aborting the init.d script, and common init.d function libraries are not safe to call with set -e in effect. For init.d scripts, it's often easier to not use set -e and instead check the result of each command separately.
This is a valid question from an interviewer standpoint because it gauges a candidates working knowledge of server-level scripting and automationAre there any code examples left?
New code examples in category Other
Relative searches
bash set -u -e
bash set+e
bash set "-e"
set -e bashh
The set -e setting for bash
shell "set -e"
what is set -e bash
set -e bash command
bash "set -e" "$?"
what's set -e bash
set -e in bash script
set -e example bash
bash script set -e
set -e meaning bash
set e bash
bash set -e meaning
bash "set -e" example
bash set-e
set -e in bash
set -e bash script
bash "set -a"
what is set -e in bash
bash set -a
bash set +e
bash set -e
set -e bash shell
set -e bash
bash set e
bash "set -e"
