That would probably be a good start. We will need to figure out how to make
things clean for shutdown. At the moment, I’m not sure we unload FSALs that
aren’t used by active exports anymore. You might want to test unexport of all
your FSAL’s exports and then see what happens when you issue your dbus command
to make sure things work cleanly.
If we need to add some unregister code we should do that. FSALs are liable to
have additional needs down the road to have dBus interfaces.
Frank
From: Sandeep Joshi [mailto:[email protected]]
Sent: Wednesday, December 14, 2016 11:42 PM
To: Frank Filz <[email protected]>
Cc: [email protected]
Subject: Re: [Nfs-ganesha-devel] notifying FSAL of config file changes
On Wed, Dec 14, 2016 at 11:46 PM, Frank Filz <[email protected]
<mailto:[email protected]> > wrote:
> Daniel,
> thx. The function which gets called on changes is fsal_ops.init_config() ,
> correct ?
That method ONLY gets called when the FSAL is loaded, so would not at all be
involved in an update.
So really, at the moment, there's no way to update the FSAL or indicate updates.
With a specific need, we can design the necessary interfaces as part of 2.5 or
future release development.
I am really looking for a way to alter FSAL parameters at runtime. I can send
in a patch if you outline the changes required. Not sure what the best way to
achieve this within the existing architecture.
Do you think calling "gsh_dbus_register_path()" within the FSAL's module init
and then using "dbus-send" from the command line would fit this use-case ?
-Sandeep
Frank
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
