In order to fix a mem leak when using notifyd I had to filter through hundreds of valgrind warnings. These were mostly mem that was allocated once at startup but never free'd - so inocent but anoying when using valgrind. So I have reduced them from ~ 350 to ~ 60. The commit "Add calls to missing object_find_destroy() to fix mem" has the mem leak that can actually grow. I'll post a smaller patch for flatiron. -Angus _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
