Bug in /etc/quotacheck
Greg Woods
woods at hao-wks.UUCP
Sat Nov 8 17:33:05 AEST 1986
In article <862 at chalmers.UUCP>, lindberg at chalmers.UUCP (Gunnar Lindberg) writes:
>
> /etc/quotacheck does not correct quota file entries for users that
> no longer owns any files in the file system.
>
> Observation:
> /etc/repquota starts reporting numerous "#1234..." entries. Using
> "find -user 1234", however, does not give anything.
I have also observed this on our VAX 11/750's running 4.2BSD (vanilla,
with some local hacks, but none in the quota system). It can be reproduced
by removing all the files for a given user ID, removing the line for that
user ID from the passwd file, and then immediately running quotacheck(8).
After that run repquota(8) and you will see the #1234.. entry for the user
you just removed. As stated, find(1) won't find any files for this user ID,
because there aren't any. I haven't tried Gunnar's fix yet, but I plan to!
--Greg
--
{ucbvax!hplabs | decvax!noao | mcvax!seismo | ihnp4!seismo}
!hao!woods
CSNET: woods at ncar.csnet ARPA: woods%ncar at CSNET-RELAY.ARPA
More information about the Comp.bugs.4bsd.ucb-fixes
mailing list