From owner-freebsd-hackers Fri Jul 19 08:09:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01142 for hackers-outgoing; Fri, 19 Jul 1996 08:09:57 -0700 (PDT) Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA01114; Fri, 19 Jul 1996 08:09:50 -0700 (PDT) Received: from localhost by troll.uunet.ca with SMTP id <21007-1788>; Fri, 19 Jul 1996 11:09:41 -0400 Date: Fri, 19 Jul 1996 11:09:37 -0400 From: Cat Okita To: "Marc G. Fournier" cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: ls ~userid no longer works... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Further to Marc's message, when logged into that machine, trying to run screen (which was working prior to whatever happened...) I get the error: > screen -R getpwuid() can't identify your account! > id uid=11(cat) gid=0(wheel) groups=0(wheel), 20(staff), 99(www) The ~userid error only appears in tcsh, but the getpwuid() error seems to be shell independant. Cat On Fri, 19 Jul 1996, Marc G. Fournier wrote: > 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... > > 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.. > > 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... > > All the appropriate NIS softare is running, my password > file on the NIS machine is fine (I can telnet/rlogin into the > machine)... > > Only ~ resolution seems to be broken... > > And I have tried to reboot the machine to see if that clears it > up, to no avail... > > I'm at a lose for where to look further, so am hoping someone > else can shed some light on the problem :(