---
** [tickets:#1134] Opensaf is coming up with the Non existing/invalid Group
Name.(devel.opensaf ticket #3050)**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Thu Sep 25, 2014 06:37 AM UTC by Hrishikesh
**Last Updated:** Thu Sep 25, 2014 06:37 AM UTC
**Owner:** nobody
changeset : 5697
Setup : 4 nodes cluster with SLES 64bit.
OPENSAF should not come up with the Non existing group name.
Steps to reproduce:- Configured OPENSAF_GROUP=xyz (which does not exists) in
nid.conf which is neither root / opensaf group. Opensaf should not be allowed
to come up with group which does not exist.
After commenting out the variable in nid.conf #export OPENSAF_GROUP=xyz,
OPENSAF is coming up successfully.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
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-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
