From owner-freebsd-current Fri Jul 19 13:53:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18732 for current-outgoing; Fri, 19 Jul 1996 13:53:37 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA18720; Fri, 19 Jul 1996 13:53:25 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id QAA01547; Fri, 19 Jul 1996 16:52:06 -0400 (EDT) Date: Fri, 19 Jul 1996 16:52:04 -0400 (EDT) From: "Marc G. Fournier" To: Bill Paul cc: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ls ~userid no longer works... In-Reply-To: <199607191620.MAA16523@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Jul 1996, Bill Paul wrote: > 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 :). > Okay, from what I can tell, something changed in libc C thta changed the behavoiur of such functions as getpwuid()...for the longest time, I could use my shared binary of bash/tcsh that was compiled under 2.1-STABLE under 2.2-CURRENT... Since they were working fine, I didn't think of checking sh/csh under -current to see if they exhibited the same behavoiur, which Cat pointed out they didn't, so I recompiled bash/tcsh out of ports and they run fine... So, chock it up to operator error...or anything else you'd like to chock it up to :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org