---
** [tickets:#3179] amf: Debug info logged with LOG_EMERG collected by journald**
**Status:** unassigned
**Milestone:** 5.20.05
**Created:** Thu Apr 23, 2020 01:04 AM UTC by Minh Hon Chau
**Last Updated:** Thu Apr 23, 2020 01:04 AM UTC
**Owner:** nobody
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
