ldconfig + SELinux = symlink slaughter

Dave Mack dmack at leviatron.com
Sat Dec 11 17:33:00 UTC 2004


OK, this is getting mildly annoying. With the current Rawhide tree (and 
for about the last week) I've been running into a problem when I "yum 
update" with SELinux in enforcing mode: the reboot which follows fails 
because most of the symlinks to shared libraries in /lib have 
evaporated. The culprit is ldconfig, which is being run during the yum 
update after library changes.

Reproduce by:

# ls -l /lib/libtermcap.so.2*

lrwxrwxrwx   1 root root 19 Dec 11 09:17   /lib/termcap.so.2 -> 
libtermcap.so.2.0.8
-rwxr-xr-x   1 root root 12952 Jun 15 17:34 /lib/libtermcap.so.2.0.8

# setenforce 1
# ldconfig

<many lines of complaint about "Input file /lib/<something>.so not found">

# ls -l /lib/libtermcap.so.2*

ls: error while loading shared libraries: libacl.so.1: cannot open 
shared object file: No such file or directory

# setenforce 0

# ldconfig

<no errors>

Now everything is back to normal.

Is anyone else able to reproduce this or is it just me? Known bug?

Dave




More information about the fedora-test-list mailing list