From owner-freebsd-questions@FreeBSD.ORG Mon Sep 27 18:06:34 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 297D516A4CE for ; Mon, 27 Sep 2004 18:06:34 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A155143D3F for ; Mon, 27 Sep 2004 18:06:33 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.11/8.12.11) id i8RI6Wnm063689; Mon, 27 Sep 2004 13:06:32 -0500 (CDT) (envelope-from dan) Date: Mon, 27 Sep 2004 13:06:32 -0500 From: Dan Nelson To: Tillman Hodgson Message-ID: <20040927180632.GD90839@dan.emsphone.com> References: <20040927164329.GA83726@seekingfire.com> <20040927170641.GB90839@dan.emsphone.com> <20040927174844.GC83726@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040927174844.GC83726@seekingfire.com> X-OS: FreeBSD 5.3-BETA5 X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: FreeBSD-Questions Subject: Re: nsswitch.conf: How does one use netgroups/over-ride passwd fields? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2004 18:06:34 -0000 In the last episode (Sep 27), Tillman Hodgson said: > I know that nsswitch.conf defaults to traditional behaviour (compat > mode). The non-compat modes are intriguing, though, and I don't know > much about them. So I thought I'd see if I can get traditional > behaviour through the newer mechanisms. This might make migrations > (for example) a bit easier. They are basically serial lookups; if a user isn't found in the first source, try the next, etc. [notfound] allows for quick termination if later sources are just fallback ones in case the primary doesn't respond. > passwd: nis [notfound=return,netgroup=dept1,dept2,admins] files > > Possibly I'm missing a point somewhere :-) What is it about netgroups > that don't make sense in an nsswitch.conf world? I have only known them to be useful as part of +/- records; for example to only allow matching users in the "access" netgroup log into a machine: +@access::0:0::: +::0:0:::/usr/local/bin/nologin It may be that netgroup's real purpose is something else that I have not yet discovered :) -- Dan Nelson dnelson@allantgroup.com