We did not implement this because we don’t track it. And we don’t track it
because there is no reason it will ever be very accurate.
The problem is that there is no reason a client need ever send an unmount, and
after a server restart, there is no reason a client need send a mount. So you
have clients that disappear without telling the server, and you have servers
that reboot, and then the clients just keep marching on without missing a beat.
So conceivably, you could have situation where if you tracked, all you would
have is clients that were in fact NOT actively using the server…
And the mount dump would not identify the NFSv4 clients…
Statistics collection should be sufficient to know who is using the server.
Frank
From: Naresh Babu [mailto:snareshb...@gmail.com]
Sent: Monday, June 5, 2017 2:51 PM
To: nfs-ganesha-devel@lists.sourceforge.net
Subject: [Nfs-ganesha-devel] reason for not implementing dump request
Hi All,
Is there a reason for not implementing dump request in NFS ganesha
(mnt_Dump.c)? Is there a place where we track mount entries?
Thanks,
Naresh
---
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
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
