From owner-freebsd-current Fri Jul 19 09:23:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA06061 for current-outgoing; Fri, 19 Jul 1996 09:23:47 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA06047; Fri, 19 Jul 1996 09:23:42 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA16523; Fri, 19 Jul 1996 12:20:12 -0400 From: Bill Paul Message-Id: <199607191620.MAA16523@skynet.ctr.columbia.edu> Subject: Re: ls ~userid no longer works... To: scrappy@ki.net (Marc G. Fournier) Date: Fri, 19 Jul 1996 12:20:10 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Jul 19, 96 11:04:13 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Marc G. Fournier had to walk into mine and say: > Hi... > > I realize that this is a really vague question, but for > some reason or another, last night, my -current machine stopped being > able to deal with a simple command such as 'ls ~userid'...it comes > back with Unknonw User... None of the code NIS code in libc has changed since before 2.1.5 was frozen (in either branch). Last bit of hacking I did was on the database cache code in ypserv. I can't see how that could cause this kind of problem (it could cause problems if I screwed up, but they'd be a bit more severe than this, I think :). > I'm running the -current machine as an NIS client off of > a -stable achine, neither of which have been upgrded in over a week.. Ah, nevermind then. I didn't change the -stable ypserv. > So far as I can tell, there is nothing that I've changed on > either of my machines in that time, as I haven't had much time to > work on either... Then maybe somebody else changed something for you. Or maybe you changed something which you think is totally unrelated but that really isn't (this is usually the case -- it's happened to me many times). Have you added any new users lately? If so, are you absitively, posolutely sure their NIS passwd entries are formatted correctly? What about group entries? Is /var/yp/