From owner-freebsd-current Sun Feb 2 9:59:15 2003 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 A8E7237B401 for ; Sun, 2 Feb 2003 09:59:11 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3549443F75 for ; Sun, 2 Feb 2003 09:59:11 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.6/8.12.6) with ESMTP id h12Hx9Xv071254; Sun, 2 Feb 2003 09:59:09 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.6/8.12.6/Submit) id h12Hx93E071253; Sun, 2 Feb 2003 09:59:09 -0800 (PST) Date: Sun, 2 Feb 2003 09:59:09 -0800 From: Steve Kargl To: Kevin Day Cc: freebsd-current@FreeBSD.ORG Subject: Re: Using 4.3-RELEASE's libc on 5.0 causes hard lockups Message-ID: <20030202175909.GA70957@troutmask.apl.washington.edu> References: <5.1.1.5.2.20030202112759.0461fcc8@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.1.5.2.20030202112759.0461fcc8@127.0.0.1> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Feb 02, 2003 at 11:41:32AM -0600, Kevin Day wrote: > > > lrwxr-xr-x 1 root wheel 9 Feb 1 00:18 libc.so -> libc.so.5 > lrwxr-xr-x 1 root wheel 16 Jul 5 2002 libc.so.3 -> /usr/lib/libc.so Delete this. > -r--r--r-- 1 root wheel 571480 Aug 5 13:45 libc.so.4 Delete this. > -r--r--r-- 1 root wheel 836892 Feb 1 00:18 libc.so.5 > > Shouldn't libc.so.4 have been a symlink to libc.so after a compat4x > install? In any case, doing that myself seemed to fix everything. The compat4x installs the libraries in /usr/lib/compat. kargl[202] ldd /usr/local/lib/NAGWare/f95 /usr/local/lib/NAGWare/f95: libm.so.2 => /usr/lib/libm.so.2 (0x28075000) libc.so.4 => /usr/lib/compat/libc.so.4 (0x28092000) What does ldd report for the binaries that die? > > My questions: > > 1) Shouldn't something along the way of doing a sysinstall upgrade or > installing compat4x have fixed /usr/lib/libc.so.4 into a symlink? (That is > the correct situation, right?) No. The reason for the version number bump from 4 to 5 is an ABI/API has changed. In this case, _stdinp, _stdoutp, and _stderrp have changed. > I know this is a pretty vague bug report, but this is a production server, > so I wasn't able to play around too much with it. I do have a backup of the > entire server before it was upgraded to 5.0 if you'd like me to check > anything there. 5.0 isn't recommended for production servers. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message