Capture and handle ldapsearch error

Since the value of $? survives command substitution and variable
assignment, we can capture and evaluate it. The next hurdle is that
by default only the return code of the last command in a pipe is
returned which is an awk in our case that will always succeed
because it'll just get no input if ldapsearch fails. This can be
worked around using shell option pipefail but this is a bashism. Instead
we go the route of writing it to a temporary file in a group command as
elsewhere in the code.

0 files changed, 0 insertions, 0 deletions