libkeyutils file size difference CentOS yum vs cPanel upcp

jack01

Well-Known Member
Jul 21, 2004
200
0
166
Hi,

I am just looking for some clarification and also reassurance about the following differences in file size of the libkeyutils*.so when reinstalling with yum, and then after upcp runs:

Code:
libkeyutils.so.1.3 file size: yum = 10192 - upcp = 12592 (CentOS 6.5 /lib64/)
libkeyutils-1.2.so file size: yum = 7176 - upcp = 9472 (CentOS 5.10 /lib64/)
libkeyutils-1.2.so file size: yum = 6404 - upcp = 7880 (CentOS 5.10 /lib/)
Thanks in advance.
 
Last edited:

jack01

Well-Known Member
Jul 21, 2004
200
0
166
Is this simply a matter of upcp replacing libkeyutils with a cPanel-specific version? Please confirm.
 

jack01

Well-Known Member
Jul 21, 2004
200
0
166
Hi cPanelMichael,

I had already seen the 'Checking your system status' page, however this is not useful to my question.

I am now specifically interested in the difference between the file sizes of the libkeyutils*.so file when installed with just a 'yum reinstall keyutils-libs' command, and then after upcp runs, as per my original post. I have done this repeatedly and the file size consistently increases slightly (again as detailed in my OP) each time I run upcp after reinstalling with yum.

All I want to know really is: 'Is it normal for cPanel upcp to install a different, slightly larger libkeyutils file (e.g. /lib64/libkeyutils.so.1.3 on CentOS 6.5) than the default CentOS yum version?'

Thanks.
 
Last edited:

quizknows

Well-Known Member
Oct 20, 2009
1,008
87
78
cPanel Access Level
DataCenter Provider
This sparked my interest.

It looks like the change is due to prelinking, so it should be harmless.

Running just this after the yum reinstall will have the same effect:

Code:
/usr/local/cpanel/scripts/rpmup
You'll notice "info [rpmup] Prelinking shared libraries and binaries: /usr/sbin/prelink -av -mR"

http://www.redhat.com/archives/rhl-list/2005-March/msg02350.html

rpm is prelink aware and during -V for prelinked binaries and shared
libraries verifies that their md5sum and filesize after unprelinking
is the same as the recorded one and that prelinking the object again
results in bitwise identical binary/library to the one present on
the filesystem.
tl;dr, don't sweat it. The file passes rpmverify both before and after the prelinking, /usr/local/cpanel/scripts/rpmup which runs as part of upcp is just prelinking the keyutils file.
 
Last edited:

jack01

Well-Known Member
Jul 21, 2004
200
0
166
Hey quizknows,

Thank you very much indeed, that makes much more sense now and helps a lot to clarify and alleviate my concern.

[Any chance of a cPanel post to confirm quizknows's clever deduction?]
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,205
363
[Any chance of a cPanel post to confirm quizknows's clever deduction?]
Yes, it's an accurate description of why the file size changes. You can verify the change in file size after reinstalling a package through YUM by running this command manually (it runs during cPanel updates):

/usr/local/cpanel/scripts/rpmup

Thank you.