As part of ticket cleanup, evaluated and decided to keep it as enhancement.
The logging should not be heavy and should only stick to state to the level of
providing hints to the user. Perhaps, the log should fall under Error category.
---
** [tickets:#340] amf: AMF API error logging is non existent**
**Status:** unassigned
**Milestone:** future
**Created:** Mon May 27, 2013 05:54 AM UTC by Praveen
**Last Updated:** Wed Jul 15, 2015 02:33 PM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/2461.
For example when an application does saAmfHealthcheckStart() with an invalid
parameter, amfnd does not log (or trace for that matter!) anything.
---
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
