resend Re: Install oddity?]
Andrew Wallace
andyw@scroom.com
Tue, 17 Apr 2001 13:59:53 -0700
> my guess is that you have multiple libcs installed, and thatlpr is
> somehow picking up an old one.
> look around /lib see if there are extra lib'c's.
Seems to be ok:
**************
[root@discipline /root]# ls -l /lib | grep -i libc
-rwxr-xr-x 1 root root 5155229 Jan 10 16:09 libc-2.2.so
lrwxrwxrwx 1 root root 11 Feb 11 21:15 libc.so.6 -> libc-2.2.so
lrwxrwxrwx 1 root root 17 Feb 11 07:26 libcom_err.so.2 -> libcom_err.so.2.0
-rwxr-xr-x 1 root root 8514 Oct 4 2000 libcom_err.so.2.0
-rwxr-xr-x 1 root root 83128 Jan 10 16:08 libcrypt-2.2.so
lrwxrwxrwx 1 root root 15 Feb 11 21:15 libcrypt.so.1 -> libcrypt-2.2.so
**************
>
> never mind. You are probably running an old lpr. Try 'which lpr'
> and the 'ls -la' the result. Is it old? is it where you exect lpr to
> be?
>
********************
[root@discipline /root]# which lpr
/usr/bin/lpr
[root@discipline /root]# ls -la /usr/bin/lpr
-rwxr-xr-x 1 lp lp 444512 Sep 25 2000 /usr/bin/lpr
[root@discipline /root]#
********************
> try rpm -q -f /wghere/your/lpr
>
> I bet it will say that no package owns it. The 'correct' lpr is
> should be in /usr/bin
********************
[root@discipline /root]# rpm -q -f /usr/bin/lpr
LPRng-3.6.24-2
********************
> (The problem is that my libc doesn't have 'stat' in it
> either. That means that stat is now defined as an inline
> function, possibly calling __stat or something like that,
> which libc does export. My guess is that the lpr you
> are invoking is compiled against a (very old) libc.
> Still, it *should* have been binary compatible.... but ...
Yeah, thanks, but it seems to still be something more
mysterious. I actually just ordered the RedHat 7.1 package,
maybe when I run the upgrade, it will be fixed. Otherwise,
I'm going to be stuck with a complete re-install. SIgh...
THanks for your help!
andy