The reason this fix is done is to prevent that the log service makes it impossible to enable long DNs. Enabling the log service for long DNs is definitely an enhancement. The problem is that currently the log, by doing a global iteration, will encounter any long DN object if it exists and then crash causing the cluster to fail to come up.
So if we regard this fix as an enhancement then we are also saying it is impossible to use long DNs in older releases if the deployment has the log service included/started. /AndersBj From: Mathi Naickan [mailto:[email protected]] Sent: den 17 augusti 2015 09:48 To: [email protected] Subject: [tickets] [opensaf:tickets] #1452 LOG: Use root name when searching for stream objects * Comment: Hi Lennart, I don't see this as a defect because there is nothing in the spec that prevents you to search from root. I think we should convert this to an enhancement. Thanks, Mathi. ________________________________ [tickets:#1452]<http://sourceforge.net/p/opensaf/tickets/1452/> LOG: Use root name when searching for stream objects Status: review Milestone: 4.7-Tentative Created: Fri Aug 14, 2015 12:34 PM UTC by elunlen Last Updated: Fri Aug 14, 2015 12:58 PM UTC Owner: elunlen At startup the log server searches for stream configuration objects. The search is done with no root object defined (NULL pointer for rootName in parameter). Search root should be "safApp=safLogService". ________________________________ Sent from sourceforge.net because [email protected]<mailto:[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.
------------------------------------------------------------------------------
_______________________________________________ Opensaf-tickets mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
