Prev: Cross compiling - size of binaries is large
Next: Windows 98SE can't access Samba (fwd)
From: Patrick Rynhart on 11 Oct 2009 18:53
Note that this file does appear to contain other functions, but the
entry point init_samba_module is missing, i.e.

# strings /usr/lib/samba/idmap/ldap.so | head
__gmon_start__
_fini
__cxa_finalize
_Jv_RegisterClasses
talloc_check_name
talloc_free
idmap_is_offline
sidmap_attr_list
get_attr_key2string
talloc_named_const

# strings /usr/lib/samba/idmap/ldap.so | grep init_samba_module

The system does report this as being a shared object/module

# file /usr/lib/samba/idmap/ldap.so
/usr/lib/samba/idmap/ldap.so: ELF 32-bit LSB shared object, Intel 80386,
version 1 (SYSV), not stripped

Regards,

Patrick

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Patrick Rynhart on 11 Oct 2009 18:53
Hi Miguel,

Thank you for your email. I'm building Samba 3.4.1 on CentOS 5.3.

I agree that my syntax isn't quite right for Samba 3.4.X. However,
looking into this matter further, I now believe that something deeper is
going wrong as I have noted the following the in logs:

Error trying to resolve symbol 'init_samba_module' in
/usr/lib/samba/idmap/ldap.so: /usr/lib/samba/idmap/ldap.so: undefined
symbol: init_samba_module

To that end:

strings /usr/lib/samba/idmap/ldap.so | grep init_samba_module

returns no result.

However, an init_samba_module entry point *is* defined for all of the
other idmap modules in this directory (i.e. adex.so, ad.so, hash.so,
ldap.so, rid.so, tdb2.so). (i.e. if I run the above command for the
other modules then I get a result for the Samba entry point)

Looks like a broken ldap.so module :-/ Where to from here!?

Thanks & Regards,

Patrick


Miguel Medalha wrote:
>
>> I've followed the instructions at
>>
>> http://wiki.samba.org/index.php/Ldapsam_Editposix
>>
>>
>>
>
> What version of Samba are you using?
>
> The wiki page you quote is now in need of urgent update. Quoting from
> the Samba 3.3.0 release notes:
>
> «
> Winbind idmap backend changes =============================
>
> The idmap configuration has changed with version 3.3 to something that
> allows a smoother upgrade path from pre-3.0.25 configurations that use
> "idmap backend". The reason for this change is that to many, also to
> Samba developers, the 3.0.25 style configuration with "idmap config"
> turned out to be very complex. Version 3.3 no longer deprecates the
> "idmap backend" parameter, instead with "idmap backend" the default
> idmap backend is specified.
>
> Accordingly, the "idmap config : default = yes" setting is no longer
> being looked at.
>
> The alloc backend defaults to the default backend, which should be able
> to allocate IDs. In the default distribution the tdb and ldap backends
> can allocate, the ad and rid backends can not. The idmap alloc range is
> now being set with the "old" parameters "idmap uid" and "idmap gid". The
> "idmap domains" parameter has been removed.
> »
>
> Release note here:
>
> http://www.samba.org/samba/history/samba-3.3.0.html
>
>

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Miguel Medalha on 11 Oct 2009 18:54

> I've followed the instructions at
>
> http://wiki.samba.org/index.php/Ldapsam_Editposix
>
>
>

What version of Samba are you using?

The wiki page you quote is now in need of urgent update. Quoting from
the Samba 3.3.0 release notes:

«
Winbind idmap backend changes =============================

The idmap configuration has changed with version 3.3 to something that
allows a smoother upgrade path from pre-3.0.25 configurations that use
"idmap backend". The reason for this change is that to many, also to
Samba developers, the 3.0.25 style configuration with "idmap config"
turned out to be very complex. Version 3.3 no longer deprecates the
"idmap backend" parameter, instead with "idmap backend" the default
idmap backend is specified.

Accordingly, the "idmap config : default = yes" setting is no longer
being looked at.

The alloc backend defaults to the default backend, which should be able
to allocate IDs. In the default distribution the tdb and ldap backends
can allocate, the ad and rid backends can not. The idmap alloc range is
now being set with the "old" parameters "idmap uid" and "idmap gid". The
"idmap domains" parameter has been removed.
»

Release note here:

http://www.samba.org/samba/history/samba-3.3.0.html


--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
 | 
Pages: 1
Prev: Cross compiling - size of binaries is large
Next: Windows 98SE can't access Samba (fwd)