Don't log EPOW event 0 (all is normal) to servicelog db.
Normally, an "all is normal" EPOW would be sent following the clearing/
handling of a non-zero EPOW condition to indicate a return to normal
condition. There are conditions such as firmware activation that triggers
spurious EPOW 0 conditions. This might confuse user. Hence don't log
EPOW 0 event to servicelog db.
This works for now, but we really need to evaluate the option of introducing
new flag to control the level of logs we log into servicelog database.
Sample console output: [root@eagle3 rtas_errd]# ./rtas_errd -d -f ../log/sample
DEBUG: handle_rtas_event(): Entering check_epow()
DEBUG: (Sequence #1000) Received EPOW action code reset (no action).
DEBUG: handle_rtas_event(): Recevied EPOW 0 (all is normal) event
DEBUG: The rtas_errd daemon is exiting. [root@eagle3 rtas_errd]# servicelog --dump [root@eagle3 rtas_errd]#
Signed-off-by: Vasant Hegde <email@example.com>
Reviewed-by: Jim Keniston <firstname.lastname@example.org>