Date: Thu, 24 Apr 2003 11:34:38 -0500 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: freebsd-current@FreeBSD.org Subject: Re: groups wrong on NIS clients Message-ID: <20030424163438.GC26825@madman.celabo.org> In-Reply-To: <20030424155855.GA74410@node1.cluster.srrc.usda.gov> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <nectar@celabo.org> http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030424163438.GC26825>