Hi, AFAIK we can run only single instance of nfs-ganesha on a given machine which supports dbus signals. Running with different ports, nfs ganesha service comes up, but the dbus signals work only for the first (primary) instance. We cannot interact with the ganesha instances (other than primary) through dbus. This is a big deal, because dynamic exports, runtime grace periods, stats, etc are not available on "secondary" ganesha instances.
I wanted to know if this is an issue at all? And is there anyone working on this already? Of the top of my head, I am thinking of handling this by adding an identifier configuration which can be appended to the bus name. For example, org.ganesha.nfsd.id1, org.ganesha.nfsd.id2, etc. Any suggestions on this approach? Can we handle it in a better way? Thanks, Sriram ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
