Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 9038 - rpc.rquotad dies after first client connects... if restarted, same thing...
rpc.rquotad dies after first client connects... if restarted, same thing...
Status: CLOSED DUPLICATE of bug 53718
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2000-02-01 04:15 EST by Vivek Sharma
Modified: 2007-04-18 12:25 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:47:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vivek Sharma 2000-02-01 04:15:38 EST
rpc.rquotad on an nfs server will die if a client of the nfs server isues
the "quota" command. This behaviour was replicated time and time again --
even updated knfsd, portmap as well as quotatools.

This becomes a mojor problem b/c all users see "no quota" when there
actually is one. So, they are unable to log into gdm etc. and are never
given any warnings.
Comment 1 Cristian Gafton 2000-08-08 22:33:50 EDT
assigned to johnsonm
Comment 2 Stephen John Smoogen 2003-01-24 11:24:57 EST
A great amount of code changes have occured in NFS, the quota package, and the
Red Hat Linux kernel since this bug was last looked at. Is it still a problem
with Red Hat Linux 8.0?
Comment 3 Matthew Miller 2003-02-21 15:13:06 EST
Is this a dupe of bug #53718? (Filed later, but has more info...)
Comment 4 Jay Turner 2003-04-14 14:06:56 EDT

*** This bug has been marked as a duplicate of 53718 ***
Comment 5 Red Hat Bugzilla 2006-02-21 13:47:37 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.