RE: .x quota definition changes

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Sergey Klyushin (Sergey.Klyushin@hummingbird.com)
Date: 10/05/01-09:04:07 AM Z


From: "Sergey Klyushin" <Sergey.Klyushin@hummingbird.com>
Subject: RE: .x quota definition changes
Date: Fri, 5 Oct 2001 10:04:07 -0400
Message-ID: <GGEOLDPPPFAMIJEOBJIBMEIEDBAA.Sergey.Klyushin@hummingbird.com>



    > -----Original Message-----
    > From: Spencer Shepler [mailto:shepler@eng.sun.com]
    > Sent: Thursday, October 04, 2001 7:15 PM
    > To: nfsv4-wg@sunroof.eng.sun.com
    > Subject: .x quota definition changes
    >
    >
    > On Thu, Sergey Klyushin wrote:
    > > typedefs of fattr4_quota_hard and fattr4_quota_soft were changed to
    > > fattr4_quota_avail_hard
    > > and fattr4_quota_avail_soft. There are also
    > > const FATTR4_QUOTA_HARD = 38; and
    > > const FATTR4_QUOTA_SOFT	= 39;
    > >
    > > Should it be changed to correspond to RFC?
    >
    > So the RFC uses "quota_avail_*" so the two const definitions should be
    > changed to something like:
    >
    > const FATTR4_QUOTA_AVAIL_HARD	= 38;
    > const FATTR4_QUOTA_AVAIL_SOFT	= 39;
    >
    > Right?
    >
    > Spencer
    >
I think so. RFC (page 39) says quota_avail_hard/quota_avail_soft. Just for
consistency.


New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-01:49:15 AM Z CST