after several years of relatively trouble free system ( 5 > 6.3 ) and port
upgrades, I started having some issues with timesieved daemon of cyrus
nothing in the software configuration has changed, but the cyrus port was
recently upgraded ( around the same time that the system was upgraded from
6.2 to 6.3 )
the only thing that looks suspicious is the fact that most ( or all )
cyrus binaries are linked to both libc5 and libc6. in fact, after some
digging around, I discovered that many other binaries on the system seem
be linked to both libraries. I suspect that libc5 is the remnant of 5x
What's the safest thing to do ?
remove libc5 and link libc5 to libc6 ?
rebuild affected software ? ( couldn't find a relevant make.conf option,
so what might a flag like that look like ? WITH_LIBC_VER=6 ?
or is there something else that can be done ?
also, it would be helpful to learn how to avoid this in the future.
Thanks a lot in advance.
libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x8814b000)
libgssapi.so.8 => /usr/lib/libgssapi.so.8 (0x88162000)
libkrb5.so.8 => /usr/lib/libkrb5.so.8 (0x88171000)
libasn1.so.8 => /usr/lib/libasn1.so.8 (0x881ab000)
libroken.so.8 => /usr/lib/libroken.so.8 (0x881d3000)
libcrypt.so.3 => /lib/libcrypt.so.3 (0x881e0000)
libcom_err.so.3 => /usr/lib/libcom_err.so.3 (0x881f9000)
libdb-4.2.so.2 => /usr/local/lib/libdb-4.2.so.2 (0x881fb000)
libssl.so.4 => /usr/lib/libssl.so.4 (0x882d0000)
libcrypto.so.4 => /lib/libcrypto.so.4 (0x88302000)
libmd.so.3 => /lib/libmd.so.3 (0x8840f000)
libwrap.so.4 => /usr/lib/libwrap.so.4 (0x8841e000)
libc.so.6 => /lib/libc.so.6 (0x88425000)
libc.so.5 => /lib/libc.so.5 (0x8851c000)
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"