Fix behavior for nfs feature #20
                
     Open
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR fixes several problematic behaviors related to
nfsfeature:tirpcorrpcsvc) is only used in NFS related code, it should not be linked ifnfsfeature is not enabled. This reduced the size and dependency and possible build errors forwebdav-server-rsbinary.nfsfeature is disabled, we should not usefs_quota_linuxto try fetching quota for NFS filesystem. It will return error code-1with messageBlock device required (os error 15), instead of1. ThereforeFqError::NoQuotawill not be returned, soFsQuota::systemnot tried.nfsfeature is enabled, we should tryFsQuota::systemas possible ifquota_nfs::get_quotais failed. In my casequota_nfs::get_quotanever worked butlibc::statvfsalways works. So, we should try as possible to uselibc::statvfsfor NFS as a fallback way.quota_nfs::get_quotafailed in different way in my environment:nfs: clnt_create erroris triggered, returningFqError::Other. In this caseFix 3would fix the problem.clnt_create, aSegmentation faultis triggered, making the thread quitted immediately, let along the code trying to callFsQuota::system.Fix 2would fix the problem.Therefore in my case, disabling
nfsfeature to uselibc::statvfswould be a better way.