Date: Thu, 11 Apr 2002 21:47:42 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: John Baldwin <jhb@FreeBSD.org> Cc: Dan Nelson <dnelson@allantgroup.com>, freebsd-hackers@FreeBSD.ORG, "Michael R. Wayne" <wayne@staff.msen.com> Subject: Re: quotactl issues Message-ID: <3CB666EE.2D4CBDEA@mindspring.com> References: <XFMail.20020411221122.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > > Note the warnx() call. It writes directly to the quota file so you can > > set quotas even if your current kernel is not capable of enforcing > > them. Is your kernel compiled with "options QUOTA"? I can tell you on > > all my 4.* systems (4.0 through 4.5) edquota calls quotactl and it > > succeeds: > > > > 90883 edquota CALL quotactl(0x8057828,0x40000,0x3e8,0x8057808) > > 90883 edquota NAMI "/usr" > > 90883 edquota RET quotactl 0 > > He didn't get EOPNOTSUPP, he got EINVAL. Perhaps it is a bug in edquota > to edit the quota file directly for an errno other than EOPNOTSUPP? "edquota" tries to do for quotas what vipw does for password entries. The file you edit is not the real "quota file", but a temp copy. For all practical purposes, you don't modify a quota until you have issued a successful "quotactl" call to set the new quota (or delete it). What's happening is expected: it's just like pwd_mkdb failing after editing the password file with vipw. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CB666EE.2D4CBDEA>