Sorry, I ran out of time & had to truncate my last comment. I'll continue here ...
Re: If you're basing this on the assumption that there aren't any "cent5"-labelled RPM's in the linux tarballs, it's an incorrect conclusion.
I'm not basing it on that, but rather on the fact that the cba8-9.00-3.30.cent6.i386.rpm inside the baseclient.tar.gz is requesting GLIBCXX objects that first showed up in libstdc++-4.4 (CentOS6).
According to rpmfind.net, libstdc++-4.1.2-54.el5 is the highest version available for CentOS5, and it simply doesn't contain the GLIBXX_3.4.11 object that the Landesk client wants.
Re: I'm assuming you're on 9.5 with Service Pack 2, yes?
Yes ... Landesk 9.5 SP2 (9.50.2.85) on Server 2008 r2
And ... Linux 2.6.18-348.18.1.el5xen #1 SMP Thu Sep 26 16:35:43 EDT 2013 i686 i686 i386 GNU/Linux CentOS release 5.9 (Final)
I am a bit suspicious about your box needing "el6" libraries - CentOS 5 usually needs "el5" ... "el6" usually indicates RHEL 6 / CentOS 6. So either there's something odd about that box, or (for whatever reason) we're detecting it (incorrectly?) to be a RHEL/CentOS 6 box, when it is a RHEL / CentOS 5 box (which may explain some of the library issues you have).
Rightfully so. It shouldn't need them. That's why I'm here.
My LanDesk correctly identifies the O/S as 'CentOS release 5.9 (Final)' but then asks for library objects that didn't exist until Cent6.
There's a few other things as well - for instance, " libc.so.6" Is provided by the "glibc-2.5-42"package on CentOS 5. "libssl.so.0.9.8" (which is what you should be needing / seeing dependency messages about) is provided by "openssl-0.9.8e-12.el5"
I have both of those libraries & they are up2date with yum, but the LD Agent is looking for objects inside those libraries that that don't exist in the Cent5 versions of them.
Instead, it's looking for objects that came inside the Cent6 versions of the libc.so.6 library. (Which is why I'm fairly certain it's the installer that's messing up. The installer chooses which rpm to install, correct)
From what I can tell, the installer is identifying a Cent5 O/S & installing rpms that call for Cent6 Library objects. That should only happen if 1) The installer was compiled with a Cent6 version of libc.so.6 , or 2) If I didn't have the libraries installed at all.
Confirm what SP-version of LANDesk you're on. Just to be on the same page.
Landesk 9.5 SP2 (9.50.2.85) on Server 2008 r2
Just as a guideline - what's the "modified date" of the BASECLIENT.TAR.GZ and the VULSCAN.TAR.GZ on your Core under (...)\LDLOGON\UNIX\LINUX\ ? That'll give us an idea what patch-level the *-IX tarballs will be roughly.
Jan 28th 2014 baseclient.tar.gz
Jan 28th 2014 vulscan.tar.gz
I think that knowing what objects are inside Francesco's libstdc++.so.6 library will tell us a lot.