From owner-freebsd-questions Thu Apr 17 00:15:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA15126 for questions-outgoing; Thu, 17 Apr 1997 00:15:09 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA15120 for ; Thu, 17 Apr 1997 00:15:07 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id AAA11434; Thu, 17 Apr 1997 00:14:58 -0700 (PDT) Date: Thu, 17 Apr 1997 00:14:58 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Adrian Chadd cc: freebsd-questions@FreeBSD.org Subject: Re: xload perm problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Apr 1997, Adrian Chadd wrote: > I've noted a lot of people installing 2.2 and 2.2.1 with the problem that > xload isn't setgid to the kmem group. > > Has this been fixed? If not, should I file a pr? It's probably that way for all X releases in this cycle. Unfortunately, I don't know if filing a PR will do anything for you; it's not directly controlled by FreeBSD per se. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major