Searched hist:"60 f53d86" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/ibm-logging/ |
| H A D | manager.hpp | 60f53d86 Wed May 23 13:23:09 CDT 2018 Matt Spinler <spinler@us.ibm.com> Restore Callout objects
Restore any saved Callout objects when the application starts
up and creates its interfaces for all existing error logs.
For each error log, it will look in the save directory for it
to find any saved Callout files. If there is one, it will
restore a Callout object from it.
The default path it looks in is:
/var/lib/ibm-logging/errors/N/callouts/ where N is an error
log entry ID.
The code will look for all numerically named files in that
directory to restore. If it is unsuccessful, it will delete
the file since it is corrupt and move on to the next one.
Tested: Restart ibm-log-manager and check that the callout
objects were preserved via looking at D-Bus.
Resolves openbmc/openbmc#2973
Change-Id: I8bc1dac3748a39e2c3a33d763e75ff90e5da668e
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
| H A D | manager.cpp | 60f53d86 Wed May 23 13:23:09 CDT 2018 Matt Spinler <spinler@us.ibm.com> Restore Callout objects
Restore any saved Callout objects when the application starts
up and creates its interfaces for all existing error logs.
For each error log, it will look in the save directory for it
to find any saved Callout files. If there is one, it will
restore a Callout object from it.
The default path it looks in is:
/var/lib/ibm-logging/errors/N/callouts/ where N is an error
log entry ID.
The code will look for all numerically named files in that
directory to restore. If it is unsuccessful, it will delete
the file since it is corrupt and move on to the next one.
Tested: Restart ibm-log-manager and check that the callout
objects were preserved via looking at D-Bus.
Resolves openbmc/openbmc#2973
Change-Id: I8bc1dac3748a39e2c3a33d763e75ff90e5da668e
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|