Description of problem:  
rquotad errors on NFS server filling up /var/log/messages.

May 13 11:28:49 <server> rpc.rquotad: Can't find filesystem
mountpoint for directory /export/rd01/stack
May 13 11:28:49 <server> rpc.rquotad: No correct mountpoint
specified.

Version-Release number of selected component (if applicable):
quota-3.09-1

How reproducible:
always

Steps to Reproduce:
1. share filesystem from server witout quotas setup
2. mount filesystem on client
3. run 'quota -v' on client
  
Actual results: 

error message on server claiming it can't find the mount point.


Expected results:

no error messages, or at least something more specific to their being
no quota files.  

Additional info:

Mounting the exported filesystem with quota options turned on and
running a 'quotacheck -acug' eliminates the problem, but creates quota
files in root directory of every exported filesystem.

The missing mountpoint error is misleading as well, initial reaction
was that it was an nfs or automount related problem.  I don't see the
need for this errror message in the first place.  If no quotas are set
up on a given exported filesystem, the rquotad daemon should just
ignore the info request... i.e. a "No quotas here" message sent back
to the client that requested the info.

Suggested fixes by other people were along the lines of shutting
rquotad off.  This isn't a good solution, because I want quotas on
exported home directories... but why should I be forced into creating
quota files for all exported filesystems just to avoid my
/var/log/messages becoming a million lines of rquota errors.  Maybe
this isn't a bug, but it certainly qualifies as a multi-celled
nuisance in my book, unless somebody can definitively explain to me
why every exported filesystem is required to have a quota file set up.