Ack from me. The IMMD side does have one depndency to SaNameT:
[saf/immsv/immd]: grep SaNameT *.h immd_cb.h: SaNameT comp_name; [saf/immsv/immd]: grep SaNameT *.c immd_amf.c:static void immd_saf_hlth_chk_cb(SaInvocationT invocation, const SaNameT *compName, SaAmfHealthcheckKeyT *checkType) immd_amf.c: const SaNameT *compName, SaAmfHAStateT new_haState, SaAmfCSIDescriptorT csiDescriptor) immd_amf.c:static void immd_amf_comp_terminate_callback(SaInvocationT invocation, const SaNameT *compName) immd_amf.c: const SaNameT *compName, const SaNameT *csiName, SaAmfCSIFlagsT csiFlags) /AndersBj -----Original Message----- From: Zoran Milinkovic [mailto:[email protected]] Sent: den 1 oktober 2014 17:25 To: Anders Widell Cc: [email protected] Subject: [devel] [PATCH 1 of 1] imm: set SA_ENABLE_EXTENDED_NAMES in immnd [#1124] osaf/services/saf/immsv/config/immnd.conf | 3 --- osaf/services/saf/immsv/immnd/immnd_main.c | 5 +++++ 2 files changed, 5 insertions(+), 3 deletions(-) Removed SA_ENABLE_EXTENDED_NAMES from immnd.conf, and set in immnd in main(). diff --git a/osaf/services/saf/immsv/config/immnd.conf b/osaf/services/saf/immsv/config/immnd.conf --- a/osaf/services/saf/immsv/config/immnd.conf +++ b/osaf/services/saf/immsv/config/immnd.conf @@ -69,8 +69,5 @@ export IMMSV_MAX_WAIT=3 # Healthcheck keys export IMMSV_ENV_HEALTHCHECK_KEY="Default" -# Uncomment the next line to enable support for extended names -#export SA_ENABLE_EXTENDED_NAMES=1 - # Uncomment the next line to enable info level logging #args="--loglevel=info" diff --git a/osaf/services/saf/immsv/immnd/immnd_main.c b/osaf/services/saf/immsv/immnd/immnd_main.c --- a/osaf/services/saf/immsv/immnd/immnd_main.c +++ b/osaf/services/saf/immsv/immnd/immnd_main.c @@ -261,6 +261,11 @@ int main(int argc, char *argv[]) daemonize(argc, argv); + if(setenv("SA_ENABLE_EXTENDED_NAMES", "1", 1)) { + LOG_ER("failed to set SA_ENABLE_EXTENDED_NAMES"); + goto done; + } + if (immnd_initialize(argv[0]) != NCSCC_RC_SUCCESS) { LOG_ER("initialize_immd failed"); goto done; ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
