From owner-freebsd-hackers  Tue Jan  2 21:15:01 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA11573
          for hackers-outgoing; Tue, 2 Jan 1996 21:15:01 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA11557
          for <hackers@freebsd.org>; Tue, 2 Jan 1996 21:14:56 -0800 (PST)
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id VAA02628; Tue, 2 Jan 1996 21:14:55 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id VAA00184; Tue, 2 Jan 1996 21:18:38 -0800 (PST)
Message-Id: <199601030518.VAA00184@corbin.Root.COM>
To: gpalmer@westhill.cdrom.com
cc: dfr@render.com, hackers@freebsd.org
Subject: Re: 2.1 panic: panic: nfsreq nogrps 
In-reply-to: Your message of "Tue, 02 Jan 96 21:10:19 PST."
             <8310.820645819@westhill.cdrom.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Tue, 02 Jan 1996 21:18:33 -0800
Sender: owner-hackers@freebsd.org
Precedence: bulk

>I just got a panic dump on one of our internal servers:
...
>panic: nfsreq nogrps

   I've already fixed this. It's caused by a setgroups(0,foo) in some program
running with uid=0. The most noteable of these is Smail, but I'm sure there
are others. If you update the server to 2.1-STABLE, the problem should go
away.

-DG