A colleague noticed after we had issues with a standard deployment we
provide to customers that libz.so was updated. Moreover ldconfig was
updated so the system uses the new libz. Again this broke a normal milk run
install we do.
Is there any reasoning for this?
Details:
The dell-system-update package 1.4.0-17.02.00 install a new version of
libz.so and update the ld config for the entire system to use it? This
breaks some programs which also use this shared library. It looks like
previous versions of dell-system-update did this with the xerces library,
which did not affect my systems, but still seems like bad practice to me.
# ldd $(which xsltproc)|grep libz
libz.so.1 => /lib64/libz.so.1 (0x0000003036600000)
# yum install dell-system-update
Resolving Dependencies
--> Running transaction check
---> Package dell-system-update.x86_64 0:1.4.0-17.02.00 will be installed
--> Finished Dependency Resolution
......
Installed:
dell-system-update.x86_64 0:1.4.0-17.02.00
# ldd $(which xsltproc)|grep libz
libz.so.1 => /usr/lib64/dsulib/libz.so.1 (0x00007f2403afe000)
# cat /etc/ld.so.conf.d/dsulib.conf
/usr/lib64/dsulib
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
