From owner-freebsd-hackers  Tue Apr  1 22:23:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA09723
          for hackers-outgoing; Tue, 1 Apr 1997 22:23:38 -0800 (PST)
Received: (from mpp@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA09717;
          Tue, 1 Apr 1997 22:23:35 -0800 (PST)
From: Mike Pritchard <mpp>
Message-Id: <199704020623.WAA09717@freefall.freebsd.org>
Subject: Re: `find . -nogroup` doesn't work?
To: dmaddox@scsn.net
Date: Tue, 1 Apr 1997 22:23:34 -0800 (PST)
Cc: hackers@FreeBSD.org
In-Reply-To: <199704020459.XAA00487@cola134.scsn.net> from "Donald J. Maddox" at Apr 1, 97 11:59:53 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Donald J. Maddox wrote:
> 
> 
>     I was attempting to use find(1) to locate files/dirs on
> my system that have bogus owners/groups, but it appears
> that the '-nogroup' and '-noowner' options don't work..
> 
>     Below is a partial listing of the files in my ghostscript
> fonts dir.  You will notice that there are a number of entries
> with unknown owners/groups: 

This is a libc problem.  The user_from_{uid,gid} routines returned
the wrong value when a non-existent user was in their internal
caches.  I just fixed it in rev 1.5 of libc/gen/pwcache.c.
--
Mike Pritchard
mpp@FreeBSD.org
"Go that way.  Really fast.  If something gets in your way, turn"