From owner-freebsd-questions Thu Mar 4 11:30: 5 1999 Delivered-To: freebsd-questions@freebsd.org Received: from proteus.idirect.com (proteus.idirect.com [207.136.80.19]) by hub.freebsd.org (Postfix) with ESMTP id 58CAF150C4 for ; Thu, 4 Mar 1999 11:30:02 -0800 (PST) (envelope-from fehr@idirect.com) Received: from bolide (bolide.idirect.com [207.136.64.241]) by proteus.idirect.com (8.9.3/8.9.3) with SMTP id OAA99399 for ; Thu, 4 Mar 1999 14:29:44 -0500 (EST) Message-Id: <3.0.5.32.19990304143033.007e8dc0@proteus.idirect.com> X-Sender: fehr@proteus.idirect.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 04 Mar 1999 14:30:33 -0500 To: freebsd-questions@freebsd.org From: "Eric D. Fehr" Subject: UID > 64K question Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why do the password file recompilation routines warn if a UID is greater than 64K, when the numeric type used for uid (uid_t) is cast as a 32 bit unsigned integer? The adduser perl script has 32000 defined as the max uid, but we have had no problems whatsoever taking this up to around 80K so far. Is it just paranoia that someone will code something that casts uid into a 16bit signed/unsigned int? Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message