Note that you have to be careful to avoid the value of VNOVAL (-1) for a
uid or a gid, or you'll run into trouble with the VFS layer; this is
arguably due to poor design of VFS. NFSv2 also had problems with reserved
values (as the NFSv2 interface greatly resembles the VFS interface, for
the obvi
On Tue, 01 May 2001 06:56:56 +0900, Yoshihiro Koya wrote:
> Hello,
> chpass: updating the database...
> pwd_mkdb: 2147483647 > recommended max uid value (65535)
Gee, that message looks familiar. ;-)
The warning was a concession that I implemented after discussions with
BDE. The way we want
Hello,
From: Sheldon Hearn <[EMAIL PROTECTED]>
Subject: Re: A question about max_uid
Date: Mon, 30 Apr 2001 09:35:50 +0200
> On Fri, 27 Apr 2001 00:15:55 +0900, Yoshihiro Koya wrote:
>
> > Currently, I have nobody (uid = 65534) account as a default account on
> > m
On Fri, 27 Apr 2001 00:15:55 +0900, Yoshihiro Koya wrote:
> Currently, I have nobody (uid = 65534) account as a default account on
> my box. It might be easy to guess that the maximum is greater than
> 65533. My question is why such a restricion still remains.
>From what I remember from my
Hello,
I found the following in the man page of pw(8).
> -u min,max, -i min,max
> These options set the minimum and maximum user and group
> ids allocated for new accounts and groups created by pw.
> The default values for each is 1000 minimum and 32000 ma
