[tickets] [opensaf:tickets] #113 Improve amf commands
- **status**: review --> fixed - **Comment**: changeset: 6793:682ba4ffc846 tag: tip user:praveen.malv...@oracle.com date:Fri Sep 11 11:55:07 2015 +0530 summary: tools/safamf: improve amf command amf-find and amf-state [#113] https://sourceforge.net/p/opensaf/mailman/message/34324500/ --- ** [tickets:#113] Improve amf commands** **Status:** fixed **Milestone:** 4.7.FC **Labels:** tools/safamf amf-find amf-state **Created:** Mon May 13, 2013 05:50 AM UTC by Nagendra Kumar **Last Updated:** Tue Aug 25, 2015 04:08 PM UTC **Owner:** Praveen Migrated from http://devel.opensaf.org/ticket/3104 amf-find can be enhanced to search with a parent/ancestor: usage: amf-find[ancestor DN] for example to search for all components in the OpenSAF NoRed? SG: $ amf-find comp safSg=NoRed?,safApp=OpenSAF === amf-state can be enhanced to search with a parent/ancestor: usage: amf-state [ [state name] [object/parent/ancestor DN]] for example to show all states for all comps in the OpenSAF 2N SG: $ amf-state comp all safSg=2N,safApp=OpenSAF The commands needs to be backwards compatible after the improvements. Other improvements to be considered! --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1475 mds: authenticate mechanism MDS code does not destroy timers
- **summary**: mds: MDS does not destroy timers --> mds: authenticate mechanism MDS code does not destroy timers - **status**: unassigned --> accepted - **assigned_to**: A V Mahesh (AVM) --- ** [tickets:#1475] mds: authenticate mechanism MDS code does not destroy timers** **Status:** accepted **Milestone:** 4.5.2 **Created:** Fri Sep 11, 2015 08:57 AM UTC by Zoran Milinkovic **Last Updated:** Fri Sep 11, 2015 08:57 AM UTC **Owner:** A V Mahesh (AVM) When start_mds_down_tmr() is called, the function creates and starts a timer. When the timer expires, the timer is stopped, but not destroyed. After using all free timers, with every start_mds_down_tmr() call, start_mds_down_tmr() allocates new timer (allocate memory). The easiest way to produce the problem is to repeatidly crash IMMA application. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1475 mds: authenticate mechanism MDS code does not destroy timers
- **status**: accepted --> fixed - **Comment**: changeset: 6794:2611051a6ffe user:A V Maheshdate:Fri Sep 11 14:27:22 2015 +0530 summary: mds: fixed memory leak in opensf authenticate code [#1475] changeset: 6795:b0bbdaadfda1 branch: opensaf-4.6.x tag: tip parent: 6777:e19e75b2852a user:A V Mahesh date:Fri Sep 11 15:22:41 2015 +0530 summary: mds: fixed memory leak in opensf authenticate code [#1475] --- ** [tickets:#1475] mds: authenticate mechanism MDS code does not destroy timers** **Status:** fixed **Milestone:** 4.5.2 **Created:** Fri Sep 11, 2015 08:57 AM UTC by Zoran Milinkovic **Last Updated:** Fri Sep 11, 2015 09:02 AM UTC **Owner:** A V Mahesh (AVM) When start_mds_down_tmr() is called, the function creates and starts a timer. When the timer expires, the timer is stopped, but not destroyed. After using all free timers, with every start_mds_down_tmr() call, start_mds_down_tmr() allocates new timer (allocate memory). The easiest way to produce the problem is to repeatidly crash IMMA application. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1476 imm: SA_IMM_ATTR_DN is not recognized as known flag
--- ** [tickets:#1476] imm: SA_IMM_ATTR_DN is not recognized as known flag** **Status:** unassigned **Milestone:** 4.6.1 **Created:** Fri Sep 11, 2015 10:47 AM UTC by Hung Nguyen **Last Updated:** Fri Sep 11, 2015 10:47 AM UTC **Owner:** nobody When creating a class that has attributes with SA_IMM_ATTR_DN flag, the following message is printed root@SC1:~# immomtest 9 1 Sep 11 17:30:39 SC1 osafimmnd[15577]: NO At least one attribute in class TestClass has unsupported attribute flag >From ImmModel::attrCreate() SaImmAttrFlagsT unknownFlags = attr->attrFlags & ~(SA_IMM_ATTR_MULTI_VALUE | SA_IMM_ATTR_RDN | SA_IMM_ATTR_CONFIG | SA_IMM_ATTR_WRITABLE | SA_IMM_ATTR_INITIALIZED | SA_IMM_ATTR_RUNTIME | SA_IMM_ATTR_PERSISTENT | SA_IMM_ATTR_CACHED | SA_IMM_ATTR_NO_DUPLICATES | SA_IMM_ATTR_NOTIFY | SA_IMM_ATTR_NO_DANGLING); SA_IMM_ATTR_DN is missing --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets