Hi, In one instance, doing a lock after unlock-in assigns QUIESCED state to the SI but not to the individual components it contains. Is this behavior correct?
Jan 26 15:51:33 node1 osafamfnd[23468]: NO Assigning 'safSi=testsu,safApp=TestApp' ACTIVE to 'safSu=testsu,safSg=testsu,safApp=TestApp' Jan 26 15:52:16 node1 osafamfnd[23468]: NO Assigned 'safSi=testsu,safApp=TestApp' ACTIVE to 'safSu=testsu,safSg=testsu,safApp=TestApp' Jan 26 15:52:34 node1 osafamfnd[23468]: NO Assigning 'safSi=testsu,safApp=TestApp' QUIESCED to 'safSu=testsu,safSg=testsu,safApp=TestApp' Jan 26 15:52:34 node1 osafamfnd[23468]: NO Assigned 'safSi=testsu,safApp=TestApp' QUIESCED to 'safSu=testsu,safSg=testsu,safApp=TestApp' -- Best Regards, Santosh ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
