- No undo logs are getting written.

- The errors and actions taken are not presented while running
InteractiveBastille so the user does not know if actions have been
correctly taken (needs to check /var/log/Bastille)
Suggestion: make BackEnd write to pipe Action&ErrorLogs when run
with InteractiveBastille and let InteractiveBastille show progress to
user
HALF FIX: Added -v option to API so that errors are printed
on stdout using GLOBAL_VERBOSE

- No verbosity levels are set, logs sometimes are too verbose and
cannot be trimed down

