There once was a capability but it never was quite right. It is gone. There is
interest in s true reload exports but it will be complicated.
Frank
Sent from my iPhone
On Sep 22, 2015, at 4:49 PM, Dirk Jagdmann <[email protected]> wrote:
> When the NFS-Ganesha server handles a SIGHUP, it should reload the
> configuration file and add new Exports and remove Exports no longer found in
> the new configuration file. However sending SIGHUP to NFS-Ganesha does not
> result in any changes to the Exports. I've tested this with version 2.2, but
> I think this behavior is not fixed on the "next" branch.
>
> Looking at the source code, from the signal handler in sigmgr_thread(),
> handling a SIGHUP calls the admin_replace_exports() function. In
> admin_replace_exports() a command for the admin thread is issued, which is
> the same as the current command, typically admin_none_pending. In the admin
> thread function admin_thread(), the while loop waits for new commands via the
> condition variable admin_control_cv, but the only command that leads to any
> action is admin_shutdown.
>
> Thus calling admin_replace_exports() results in no further action done on the
> admin thread.
>
> I also did not find any function that would actually re-load the
> configuration file, re-parse the EXPORT blocks and add/remove anything new.
> Does such a function exist and just needs to be called from the admin thread?
>
> —
> Reply to this email directly or view it on GitHub.
>
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Nfs-ganesha-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
