[Samba] trouble with shadow_copy2

[Alexander Harm || ApfelQ]

Looks all good to me. /lib is symlinked to /usr/lib and ld.so.conf contains all three paths (/usr/local/lib, /lib, /usr/lib)...

I will increase the logging and play a bit more...

> On Thursday, Dec 08, 2022 at 4:20 PM, Michael Tokarev <mjt at tls.msk.ru (mailto:mjt at tls.msk.ru)> wrote:
> 08.12.2022 18:13, Michael Tokarev wrote:
> ..
> > I know only one thing: your /lib/x86_64-linux-gnu/libsmbconf.so.0 is older
> > than needed by shadow_copy2. Find out why. I don't have access to your system.
> >
> > Note that samba itself is starting (or it looks like, - I don't know), and
> > if it is 4.17, it too needs a more recent version of libsmbconf.so.0, so there's
> > a question how did you manage to start samba with this libsmbconf if it is 4.17
> > samba.
>
> Adding another data point. It reports "/lib/x86_64-linux-gnu/", not the
> usual "/usr/lib/x86_64-linux-gnu/". This is why I asked about a broken
> merged-/usr. On my system with merged-usr, /lib is a symlink to /usr/lib,
> and /etc/ld.so.conf directs the runtime linker to /usr/lib/x86_64.. first
> anyway, so the first thing it tries to load is /usr/lib/$multiarch/libfoo.so,
> and if that fails, it goes to /lib/$multiarch/libfoo.so.
>
> The question is what happened with /usr/lib/$multiarch/libsmbconf.so.o, and
> how that happened there's older /lib/$multiarch/libsmbconf.so.0.
>
> This is all very basics. Only you can explore your system.
>
> /mjt