Date: Sat, 31 Jul 1999 13:39:16 -0400 (EDT) From: Adrian Filipi-Martin <adrian@ubergeeks.com> To: "Matthew D. Fuller" <fullermd@futuresouth.com> Cc: Mike Smith <mike@smith.net.au>, Sheldon Hearn <sheldonh@uunet.co.za>, hackers@FreeBSD.ORG Subject: Re: No MAXUID ? Message-ID: <Pine.BSF.4.05.9907311333010.33274-100000@thneed.ubergeeks.com> In-Reply-To: <19990730145410.M24560@futuresouth.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 30 Jul 1999, Matthew D. Fuller wrote: > On Fri, Jul 30, 1999 at 09:13:52AM -0700, a little birdie told me > that Mike Smith remarked > > > > I think that the administrator should be forced to override the warning > > manually to indicate that they are aware of the issues they are getting > > themselves in for, or at the very least that there should be some very > > serious warnings placed in the relevant manpages (mount_nfs, passwd(5), > > vipw, etc) covering these issues.a > > How about a bit of a compromise on it? > Make pwd_mkdb just spew a warning like > --- > WARNING: UID(s) over XXXXX detected, may cause problems. > --- > by default, with a flag (-v?) to list the specific ones causing problems. > > Warning in manpages are, of course, always a Good Thing. I'd be in favor of adding a /etc/pwd_mkdb.conf or some similar file. Then the behavior could be easily configured for your environment with something like "32bit_uid_ok=yes" dirrective in the file. Even an environment variable could work. I have thought about making such a file to avoid recompiling pwd_mkdb with different defaults for large passwd files. The defaults get tiring when using vipw. A save can take 30 seconds on some of our sytstems. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] 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?Pine.BSF.4.05.9907311333010.33274-100000>