Hi,
In our application we open many sections and write to it. When application is restarted we call saCkptSectionIterationInitialize() and saCkptSectionIterationNext() to loop through all the sections and reinitialize application to its original state. When only one application process opens sections, restarts and iterates, behavior is as expected. When we fork child process from application, restart application, and iterate section from restarted application process (while child process is still running) the first section descriptor returned is not the first section instead it is some other section. One experiment we did was to kill child process before the restarted application does checkpoint open, then iteration was as expected. Is it valid for multiple process to open same checkpoint? Is it architecturally supported? In general apart from section iteration what are the other consequences of accessing same checkpoint from multiple processes? Is above described iteration behavior as expected? Are there any work around/solution to fix the iteration behavior in the second case? Regards, Girish -- . ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
