Fix logging in vbmcd
Currently we log any exceptions as INFO and without much details. Start logging them as ERROR with tracebacks. Add missing logging. However, don't treat KeyboardInterrupt as an exception, just exit. Also log the successful start-up, its absence is confusing. Change-Id: I7464ce425ed05248152f264d64950e0ab1c0aec0changes/03/711203/1
parent
834d02e616
commit
b12197bb0d
Loading…
Reference in New Issue