From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 21:12:31 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6B2616A419 for ; Wed, 26 Sep 2007 21:12:31 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mx1.freebsd.org (Postfix) with ESMTP id C45FE13C45B for ; Wed, 26 Sep 2007 21:12:31 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mail.rsync.net (8.12.11/8.12.11) with ESMTP id l8QLL3Qe071115; Wed, 26 Sep 2007 14:21:03 -0700 (PDT) (envelope-from info@rsync.net) Received: from localhost (info@localhost) by mail.rsync.net (8.12.11/8.12.11/Submit) with ESMTP id l8QLL3Cl071112; Wed, 26 Sep 2007 14:21:03 -0700 (PDT) (envelope-from info@rsync.net) X-Authentication-Warning: mail.rsync.net: info owned process doing -bs Date: Wed, 26 Sep 2007 14:21:03 -0700 (PDT) From: "rsync.net" To: Julian Elischer In-Reply-To: <46FAC866.5050602@elischer.org> Message-ID: <20070926141636.P21960@mail.rsync.net> References: <20070925093722.N21960@mail.rsync.net> <46FAA37B.3020903@elischer.org> <20070926130845.U21960@mail.rsync.net> <46FAC866.5050602@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Thu, 27 Sep 2007 12:09:16 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 21:12:32 -0000 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? We have no idea. All we know is, we need some UIDs to be members of more than 16 groups, and that is currently impossible. We are happy to lend financial support to a solution ... however it sounds like $500 and free rsync.net storage space isn't going to be sufficient ? Is it unexpected that someone has run into this limit ?