Hi Anders,
The way it is currently designed is if you turn on PLM at
build-time, it will link with both OpenHPI and libvirt.
They are both needed. The libvirt functions are used for performing
admin operations on the virtualized EEs, and OpenHPI is used for
non-virtualized EEs
Summary: log: support DNs longer than 255 bytes [#1315]
Review request for Trac Ticket(s): #1315
Peer Reviewer(s): Mahesh, Lennart
Pull request to: <>
Affected branch(es): default
Development branch: default
Impacted area Impact y/n
osaf/services/saf/logsv/lgs/Makefile.am |1 +
osaf/services/saf/logsv/lgs/lgs.h |4 +-
osaf/services/saf/logsv/lgs/lgs_amf.cc | 14 +-
osaf/services/saf/logsv/lgs/lgs_config.cc | 30 +-
osaf/services/saf/logsv/lgs/lgs_evt.cc | 77 --
osaf/libs/agents/saf/lga/Makefile.am |1 +
osaf/libs/agents/saf/lga/lga.h |5 +-
osaf/libs/agents/saf/lga/lga_api.c | 110 ++
osaf/libs/agents/saf/lga/lga_mds.c | 168 +-
osaf/libs/agents/saf/lga/lga_state.c |7 +-
tests/logsv/Makefile.am | 4 +-
tests/logsv/logtest.c| 132 +--
tests/logsv/tet_LogOiOps.c | 2 +-
tests/logsv/tet_Log_recov.c |17 +-
tests/logsv/tet_log_longDN.c | 1226 ++
osaf/tools/saflog/saflogger/Makefile.am | 1 +
osaf/tools/saflog/saflogger/saf_logger.c | 90 ++-
2 files changed, 75 insertions(+), 16 deletions(-)
With app stream, saflogger used app stream DN as logFileName.
With Long DN, the app stream DN could be longer than
All fencing requests go through the opensaf_reboot script today.
Have you thought about build-time options for how to link with these two
libraries? I suppose the most flexible approach would be build-time
options to select which libraries to link with (so you can select to
link with just one
