From owner-freebsd-current@FreeBSD.ORG Thu Apr 24 09:34:40 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2CEC37B405 for ; Thu, 24 Apr 2003 09:34:40 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1FB943FD7 for ; Thu, 24 Apr 2003 09:34:39 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id 3A5414D for ; Thu, 24 Apr 2003 11:34:39 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id C0E1578C66; Thu, 24 Apr 2003 11:34:38 -0500 (CDT) Date: Thu, 24 Apr 2003 11:34:38 -0500 From: "Jacques A. Vidrine" To: freebsd-current@FreeBSD.org Message-ID: <20030424163438.GC26825@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , freebsd-current@FreeBSD.org References: <20030423210539.GA1348@node1.cluster.srrc.usda.gov> <20030423215038.GB22152@madman.celabo.org> <20030423220754.GA16387@node1.cluster.srrc.usda.gov> <20030423221120.GA22798@madman.celabo.org> <20030423221915.GA17543@node1.cluster.srrc.usda.gov> <20030424020829.GA73546@madman.celabo.org> <20030424155855.GA74410@node1.cluster.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030424155855.GA74410@node1.cluster.srrc.usda.gov> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 Subject: Re: groups wrong on NIS clients X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2003 16:34:41 -0000 On Thu, Apr 24, 2003 at 10:58:55AM -0500, Glenn Johnson wrote: > > The only thing I can think of that might give you different results > > when logging in via the console versus via sshd is if the latter > > cannot contact the NIS server for some reason. Do you see (e.g. with > > tcpdump) any NIS queries when you attempt to login via ssh? > > Yes, I get messages like the following: > > 10:28:15.092664 node1.cluster.srrc.usda.gov.nfs > node11.cluster.srrc.usda.gov.207013284: reply ok 116 lookup ERROR: No such file or directory This is not NIS. This is NFS, a `file not found' error. > > If you want to dig deeper, you should arrange for sshd to spit out the > > group list. > > I will gice that a try. Thanks! Cheers, -- Jacques A. Vidrine http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se