we have many modules which are regestring more then one name. e.g. pdb_ldap: "ldapsam" ,"ldapsam_compat" auth_sam: "sam","samstrict" ... if someone build pdb_ldap, auth_sam or ... as shared modules he *HAVE* isn't able to load this modules... because there's no $libdir/pdb/ldapsam_compat.so file or $libdir/auth/samstrict.so file... The only thing that would work is to use the 'preload modules' parameter, but the preload modules are only loaded by smbd for now. so pdbedit or something like that will fail to load ldapsam_compat!!! I would preferr to install symlinks for this places... I think its a *must* to fix that before 3_0! metze
Should be a higher priority to get this working. Note that statically built modules are ok.
installation issue
Is this still a bug?
Yes, it is still a bug...
Fixed in CVS. We create symlinks now.
originally reported against 3.0aph24. Bugzilla spring cleaning. Removing old alpha versions.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.