Hi,
frantisek holop <min...@obiit.org> wrote:
| hi there,
[.]
| could the reason be, that after the update both
| libkvm.so.13.0 and libkvm.so.13.1 were still under /usr/lib?
The dynamic linker will use the first library it encounters to
resolve the symbols (which can be used for nice tricks via some
LD_PRELOAD environment, if supported by the link mechanism).
ldd(1) shows up which library is linked into a program (or other
dynamic library):
?0%0[steffen@obsdc steffen]$ ldd /usr/bin/systat
/usr/bin/systat:
Start End Type Open Ref GrpRef Name
0000000000400000 0000000000824000 exe 1 0 0 /usr/bin/systat
0000000200a0c000 0000000200e65000 rlib 0 1 0
/usr/lib/libcurses.so.12.1
000000020ccf8000 000000020d120000 rlib 0 1 0
/usr/lib/libm.so.7.0
0000000200602000 0000000200a0c000 rlib 0 1 0
/usr/lib/libkvm.so.13.1
000000020c812000 000000020ccf8000 rlib 0 1 0
/usr/lib/libc.so.64.0
000000020c400000 000000020c400000 rtld 0 1 0
/usr/libexec/ld.so
So the answer to the question above is "no".
However, file descriptor reference counting changed recently and
if an old libkvm would work with a new kernel then this could
surely result in "such behaviour" (let me quote this as i don't
know the real codeflow, please).
According to my plus log all that work has been done rather
atomically on 2012-05-01, though.
| -f
| --
| death is proven to be 99.9% fatal to all laboratory rats.
I think i belong to the other 0.1%.
Thanks
--steffen
Forza Figa!
