Samba4 nmbd/smbd/winbindd
Günter Kukkukk
linux at kukkukk.com
Mon Aug 27 18:13:44 MDT 2012
Am Montag, 27. August 2012, 08:37:45 schrieb Marc Muehlfeld:
> Am 27.08.2012 08:29, schrieb Ricky Nance:
> >>> From many years samba3 practice i also used copy to place that
> >>>
> >>> dynlib into /lib/ - and failed badly some days ago.
> >>>
> >>> So one should use symbolic links - as already posted in this thread.
> >>
> >> This is a good advice. But this only meets s4 installations, right? For
> >> my s3 installations here, the libnss_winbind.so is not copied by make
> >> install somewhere where I can link to. It's only in the sources folder.
> >> Is this right?
> >
> > No this should work for all samba installs.
>
> But for s3 installations the libnss_winbind.so stays in the sources folder
> (what have different names for every version) here, and is not copied by
> make install:
>
> # find / -name libnss_winbind.so
> /usr/src/samba-3.5.17/nsswitch/libnss_winbind.so
> /usr/src/samba-3.5.16/nsswitch/libnss_winbind.so
>
> Putting a link in /lib to a file in the source folder makes it useless when
> updating to a new version.
>
> Or do I missunderstand anything?
>
>
> Regards,
> MArc
Hi Marc,
to clarify the current situation.
Atm there are 2 possibilities to build samba3:
1. in the top level build dir using WAF (future default build)
- ./configure <prefix and options> or ./configure.developer <prefix and options>
- make
- make install (usually as root)
This WAF build is building both samba3 and samba4!
But the resulting samba3 code is _not_ the same as when using the
next option. More optimization is done and ABI version info can be used.
Take care with such an installed libnss_winbind.so.2 (and don't use the one
from the build dir!)
2. from the top level build dir
- cd source3/
- ./autogen.sh
- ./configure <prefix and options> or ./configure.developer <prefix and options>
- make
- make install (usually as root)
The generated dynlib <top level>/nsswitch/libnss_winbind.so can be copied to
/lib/libnss_winbind.so.2
It does not contain any external references to other samba dynlibs.
ldd libnss_winbind.so
linux-gate.so.1 => (0xffffe000)
libc.so.6 => /lib/libc.so.6 (0xb7694000)
/lib/ld-linux.so.2 (0xb7834000)
compared to the one from the WAF build:
ldd /lib/libnss_winbind.so.2
linux-gate.so.1 => (0xffffe000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7763000)
libwinbind-client.so => /usr/local/samba/lib/private/libwinbind-client.so (0xb775f000) !!!
libc.so.6 => /lib/libc.so.6 (0xb75f2000)
/lib/ld-linux.so.2 (0xb77a4000)
Hope this helps. :-)
Cheers, Günter
More information about the samba-technical
mailing list