Fixed journal flooding of SSL messages

The problem was that when a curl command
was given without any options, several error
messages would be thrown that can flood the
journal.  To fix this I had to use a 'try
catch' statment to catch the error.  I
modified the current 'try catch' statement
to catch and pass on the ssl error so no
error messages of that kind could flood the
journal.  After implementation no more ssl
error messages were flooding the journal,
however a new error was thrown so I had to
create an additional exception and pass on
it as well.  This fixes issue number 583.

Resolves openbmc/openbmc#583

Change-Id: I4857861f3c0ff103e2bccf9f5a5821c8219aefe6
Signed-off-by: Josh King <jdking@us.ibm.com>
2 files changed
tree: d789ee991a11e3b053def5a8942656ab6c5f2c40
  1. classes/
  2. common/
  3. conf/
  4. COPYING.apache-2.0
  5. COPYING.MIT
  6. LICENSE