OpenWrt Forum Archive

Topic: samba3 can't load library 'libsasl2.so.2'

The content of this topic has been archived on 4 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

who have the lib file libsasl2.so.2?



belkin 7231-4p
dd-wrt rc4 mini

thttpd ftpd mldonkey is running ok!!

The samba2 is running ok!!

But the samba3 is running badly!


root@DD-WRT:~# /opt/bin/ipkg-opt install /jffs/samba_3.0.28-1_mipsel.ipk
Installing samba (3.0.28-1) to root...
Configuring atftp
postinst script returned status 1
ERROR: atftp.postinst returned 1
Configuring samba
The original samba version 2 config (/etc/samba/smb.conf) is no longer
working with this version of samba.
Please create a new samba version 3 config (/opt/etc/samba/smb.conf).
After verify your smb.conf file, modify and execute /opt/etc/init.d/S08samba
to activate the samba version 3.
Successfully terminated.
root@DD-WRT:~# /opt/etc/init.d/S08samba
root@DD-WRT:~# /opt/etc/init.d/S08samba
Starting nmbd:
/opt/sbin/nmbd: can't load library 'libsasl2.so.2'
Starting smbd:
/opt/sbin/smbd: can't load library 'libsasl2.so.2'



root@DD-WRT:~# /opt/bin/ipkg list_installed
atftp - 0.7-7 -
busybox - 1.5.0-1 -
busybox-base - 1.5.0-1 -
busybox-links - 1.5.0-1 -
bzip2 - 1.0.4-1 -
cups - 1.3.4-1 -
e2fsprogs - 1.40.2-1 -
expat - 2.0.1-1 -
fontconfig - 2.3.2-5 -
freetype - 2.1.10-4 -
gconv-modules - 2.2.5-7 -
gnutls - 1.6.3-1 -
libcurl - 7.16.4-1 -
libgcrypt - 1.2.4-1 -
libgd - 2.0.35-1 -
libgpg-error - 1.4-1 -
libidn - 1.0-1 -
libjpeg - 6b-2 -
libpng - 1.2.19-1 -
libtasn1 - 0.3.10-1 -
libtiff - 3.8.2-1 -
libuclibc++ - 0.2.2-4 -
make - 3.81-1 -
nano - 2.0.6-1 -
ncurses - 5.6-1 -
openldap-libs - 2.3.38-1 -
openssl - 0.9.7m-2 -
pcre - 7.4-1 -
popt - 1.7-2 -
proftpd - 1.3.1-2 -
readline - 5.2-2 -
samba - 3.0.28-1 -
squid - 2.6.16-1 -
thttpd - 2.25b-5 -
uclibc-opt - 0.9.28-12 -
wget - 1.10.2-4 -
wxbase - 2.8.0-5 -
xinetd - 2.3.14-7 -
zlib - 1.2.3-2 -
Successfully terminated.

up

This is neither the DD-WRT, nor the Optware forum. Please direct your question elsewhere

The discussion might have continued from here.