[There's no component defined in bugzilla for smbwrapper..]

smbwrapper.so and smbsh will not work with some applications because symbols it 
uses will clash, leading to mysterious core dumps.

(rsync is a great example, as it shares a common author who names functions in 
very similar ways... it will crash when the smbwrapper code calls 
open_socket_out() - itself a clash - and ends up executing rsync's own 
vsnprintf routine and then smbwrapper's dopr())

One way to fix this is to prefix colliding symbols, within the Samba code, but 
to be safe this really requires every function and global variable to be 
changed and that is messy.

I think the *correct* way to solve this, on platforms that permit it, is to 
link the smbwrapper.so shared object explicitly specifying which symbols are to 
be global.

For Solaris, this can be done with the following patch to Makefile.in (this 
will probably need some autoconf work for portability):

[This problem also appears to be present in Samba 3.x]

--- Makefile.in.orig	Thu Jan  8 10:34:40 2004
+++ Makefile.in	Thu Jan  8 12:40:13 2004
@@ -639,7 +639,8 @@
 
 bin/smbwrapper.@SHLIBEXT@: $(PICOBJS) bin/.dummy
 	@echo Linking shared library $@
-	@$(SHLD) @LDSHFLAGS@ -B local -o $@ $(PICOBJS) $(LDFLAGS) $(LIBS) \
+	@nm smbwrapper/wrapped.po | $(AWK) -F\| 'BEGIN { 
printf "{\nglobal:\n" } $$5 ~ /GLOB/ { if ( $$7 !~ /UNDEF/ ) { printf "%s;\n", 
$$NF }} END { printf "local: *;\n};\n" }' > smbwrapper/mapfile
+	@$(SHLD) @LDSHFLAGS@ -M smbwrapper/mapfile -o $@ $(PICOBJS) $(LDFLAGS) 
$(LIBS) \
 		@SONAMEFLAG@`basename $@`
 
 bin/smbwrapper.32.@SHLIBEXT@: $(PICOBJS32) bin/.dummy