I'm curious as to how other Linux admins manage
/etc/ld.so.conf and in general, shared libraries across multiple Linux servers.
We have about 30-40 Linux servers running SLES 11. Since they are tied to Active Directory, users can log into any server with their same credentials. Originally, each server had its own local
ld.so.conf. However, we ran into issues where a specific piece of software, php for example, would run on server X but crash on server Y because a sys admin rearranged
ld.so.conf on server Y. We strive for consistency across servers so users can easily use any number of servers for load balancing. There are certain servers that have specific purposes of course though.
We thought symlinking to a shared
ld.so.conf with a script that goes out and runs
ldconfig on all servers whenever a change is made. I thought it would bring consistency across all servers, but I see how some servers would need a custom
ld.so.conf because it runs different software that may need a different lib version.
I've only been a Linux admin for under three years, so this may be a simple answer for some, so just looking for advice on this topic. Questions that came to mind:
- local or symlinked
- clean out old versions of shared libs if multiple versions exist in different lib directories?