Commit [ecc702]  Maximize  Restore  History

rtas_errd: Don't log normal EPOW events

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.

Note:
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
<snip>
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 <hegdevasant@linux.vnet.ibm.com>
Reviewed-by: Jim Keniston <jkenisto@linux.vnet.ibm.com>

Vasant Hegde Vasant Hegde 2014-01-21

changed rtas_errd/epow.c
changed rtas_errd/rtas_errd.c
changed rtas_errd/rtas_errd.h
rtas_errd/epow.c Diff Switch to side-by-side view
Loading...
rtas_errd/rtas_errd.c Diff Switch to side-by-side view
Loading...
rtas_errd/rtas_errd.h Diff Switch to side-by-side view
Loading...

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks