Date: Fri, 24 Oct 2014 10:56:51 +0200 From: "Ronald Klop" <ronald-lists@klop.ws> To: "FreeBSD Stable" <freebsd-stable@freebsd.org>, "Tim Daneliuk" <tundra@tundraware.com> Subject: Re: /usr/lib/pam_opie.so.5: Shared object "libopie.so.8" not found Message-ID: <op.xn78g1wekndu52@ronaldradial.radialsg.local> In-Reply-To: <5447F802.6010600@tundraware.com> References: <5447EFD2.9000609@tundraware.com> <op.xn481vopkndu52@82-171-231-144.ip.telfort.nl> <5447F802.6010600@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 22 Oct 2014 20:31:30 +0200, Tim Daneliuk <tundra@tundraware.com>
wrote:
> On 10/22/2014 01:16 PM, Ronald Klop wrote:
>> On Wed, 22 Oct 2014 19:56:34 +0200, Tim Daneliuk
>> <tundra@tundraware.com> wrote:
>>
>>> I mentioned this yesterday and someone suggested a fix had been
>>> committed ...
>>> Well, not so much as of FreeBSD 10.1-PRERELEASE #2 r273434.
>>>
>>> This is still breaking cron and saslauthd, for example.
>>>
>>> The workaround is an appropriate entry in /usr/local/etc/libmap.d of
>>> the form:
>>>
>>> libopie.so.8 libopie.so.7
>>>
>>>
>>
>> Rebuild the port for saslauthd so it will pick up the right version of
>> libopie
>> again.
>
>
> The particular error I saw was from cron, so doing what you suggest will
> not
> fix all use cases.
/usr/sbin/cron is not directly linked to libopie.
$ ldd -a /usr/sbin/cron
/usr/sbin/cron:
libpam.so.5 => /usr/lib/libpam.so.5 (0x20043000)
libutil.so.9 => /lib/libutil.so.9 (0x20057000)
libc.so.7 => /lib/libc.so.7 (0x20071000)
/usr/lib/libpam.so.5:
libc.so.7 => /lib/libc.so.7 (0x20071000)
/lib/libutil.so.9:
libc.so.7 => /lib/libc.so.7 (0x20071000)
But depending on your pam configuration some dependency might be
dynamically loaded. Like this:
$ ldd -a /usr/lib/pam_opie.so.5
/usr/lib/pam_opie.so.5:
libopie.so.7 => /usr/lib/libopie.so.7 (0x801602000)
libpam.so.5 => /usr/lib/libpam.so.5 (0x80180b000)
libc.so.7 => /lib/libc.so.7 (0x80081f000)
/usr/lib/libopie.so.7:
libmd.so.6 => /lib/libmd.so.6 (0x801a17000)
libc.so.7 => /lib/libc.so.7 (0x80081f000)
/usr/lib/libpam.so.5:
libc.so.7 => /lib/libc.so.7 (0x80081f000)
/lib/libmd.so.6:
libc.so.7 => /lib/libc.so.7 (0x80081f000)
So rebuild those and things should be resolved again.
Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.xn78g1wekndu52>