From owner-freebsd-hackers Sat Jul 31 16: 7:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id D12BA14E3D for ; Sat, 31 Jul 1999 16:07:22 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-158.skylink.it [194.185.55.158]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id BAA20765; Sun, 1 Aug 1999 01:06:16 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id AAA19452; Sun, 1 Aug 1999 00:56:10 +0200 (CEST) Date: Sun, 1 Aug 1999 00:56:10 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Sheldon Hearn Cc: Adrian Filipi-Martin , "Matthew D. Fuller" , Mike Smith , hackers@FreeBSD.ORG Subject: Re: No MAXUID ? In-Reply-To: <69079.933455100@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'd be in favor of adding a /etc/pwd_mkdb.conf or some similar > > file. ... > While warnings and error messages should give me enough information > to address a problem efficiently (something on the wishlist of any > Wintendo administrator), once I know there is more than zero potentially > problematic entries, I can used cat, awk and sh to find all the culprits > if I want to. What we are looking at is a warning for potential problems with legacy tools. Yet another configuration file is not going to make our life any easier. What Sheldon proposed was to get rid of n-1 messages out of n. Maybe there is a good reason to have a config file, but this does not sound like one. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message