Date: Wed, 26 Sep 2007 14:00:22 -0700 From: Julian Elischer <julian@elischer.org> To: "rsync.net" <info@rsync.net> Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? Message-ID: <46FAC866.5050602@elischer.org> In-Reply-To: <20070926130845.U21960@mail.rsync.net> References: <20070925093722.N21960@mail.rsync.net> <46FAA37B.3020903@elischer.org> <20070926130845.U21960@mail.rsync.net>
next in thread | previous in thread | raw e-mail | index | archive | help
rsync.net wrote: > > On Wed, 26 Sep 2007, Julian Elischer wrote: > >> rsync.net wrote: >>> It has been impossible to change kern.ngroups - at least for several years >>> now. It was not fixed in either 5.x or 6.x : >>> >>> http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html >>> >>> It is seemingly a difficult problem: >>> >>> http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] >>> >>> However it should be solved - we can't be the only ones out there trying >>> to add a UID to more than 16 groups... >> the big question is what do you do for NFS? remember something about >> it only having a fixed storage for groups. > > > (snip) > > >>> [1] Is it indeed true that these programs are broken by not following >>> NGROUPS_MAX from syslimits.h? > > > Assuming the answer to the above footnote is "yes", would it be reasonable > to fix the OS generally, but continue to hard code the limits in things > like NFS ? > > Are you saying that, unlike other items, NFS _does_ respect NGROUPS_MAX ? actually it doesn't see: nfs/rpcv2.h:#define RPCAUTH_UNIXGIDS 16 but what do we do if a user has > 16?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46FAC866.5050602>