Config callbacks are called per-block, so if a block relevant to a FSAL changes (an export with that FSAL, or that FSAL's FSAL block), the the callback for that block will be called. There's no general notifications when config changes.
Daniel On 12/13/2016 05:12 AM, Sandeep Joshi wrote: > > Does Ganesha call some method to notify an individual FSAL if the config > file has changed ? I am referring to operations other than adding and > deleting exports. > > What is the recommended way to achieve this function ? > > It seemed like fsal_ops.init_config() is called on fsal_commit() but not > sure if this gets called on reread_log_config() in the signal manager > thread. > > -Sandeep > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
