commit de12a988951315e49b7f18c01c347e3c73bc1837
Author: Peter McIntyre <[email protected]>
Date: Thu Apr 30 15:28:22 2020 +1000
amfd: change LOG_EM to LOG_ER [#3179]
Many places in amf code the debug info is logged with LOG_EMERG,
which is not quite informative at emergency level. These should be moved to
LOG_ERR level.
The fix is to change the LOG_EM to the LOG_ER level.
---
** [tickets:#3179] amf: Debug info logged with LOG_EMERG collected by journald**
**Status:** assigned
**Milestone:** 5.20.05
**Created:** Thu Apr 23, 2020 01:04 AM UTC by Minh Hon Chau
**Last Updated:** Fri Apr 24, 2020 02:01 AM UTC
**Owner:** Peter McIntyre
It mostly happens many places in amf code that the debug info is logged with
LOG_EMERG, it ends up being collected by journald which is not quite
informative at emergency level.
LOG_EM("%s:%u: %u", __FILE__, __LINE__,
n2d_msg->msg_info.n2d_data_req.param_info.attr_id);
It also depends on journald configuration to pick up which level of logging,
but this kind of logging with __FILE__/__LINE__ is bit too 'high' as EMERG,
which could be at level of WARN or ERR.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list._______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
