Hi Operating file on Samba-server from Client fail, when I try to change attribute of file.(ex, Read only/Hidden/Archive) Error message found at /usr/local/samba/var/'client-pc-name'.log === /usr/local/samba/var/'client-pc-name'.log === [2007/08/23 13:26:19, 1] smbd/service.c:make_connection_snum(1033) 'client-pc-name' (xxx.xxx.xxx.xxx) connect to service ufsshare initially as user test (uid=100, gid=10) (pid 1640) ld.so.1: smbd: fatal: relocation error: file /usr/local/samba/lib/vfs/solarisacl.so: symbol aclsort: referenced symbol not found === /usr/local/samba/var/'client-pc-name'.log === I tried to know about symbol aclsort, and "man aclsort" told me that symbol aclsort need "-lsec" when compile. So, I edited line 20 of Makefile and build again, it works. before > LIBS=-lsendfile -lresolv -lnsl -lsocket after > LIBS=-lsendfile -lresolv -lnsl -lsocket -lsec Is it correct? If there is better solution, please let me know. --- Server OS : Solaris 10 11/06 Samba Server : Samba-3.025c : download from http://us3.samba.org/samba/ftp/stable/samba-3.0.25c.tar.gz Windows Client : Windows XP SP2 configure : ./configure –with-shared-modules=vfs_zfsacl,vfs_solarisacl --- smb.conf # Samba config file created using SWAT # from xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) # Date: 2007/08/23 13:48:24 [global] dos charset = CP932 unix charset = EUC-JP workgroup = MYGROUP netbios name = SAMBA server string = Samba Server interfaces = ce1 bind interfaces only = Yes log file = /usr/local/samba/var/log.%m max log size = 50 dns proxy = No ldap ssl = no [zfsshare] comment = ZFS volume path = /export/zhome1 read only = No vfs objects = zfsacl [ufsshare] comment = ufs volume path = /export/uhome1 read only = No vfs objects = solarisacl
Hi, apparently building the posix acl vfs modules (like vfs_solarisacl) as shared modules has not been tested: by default, once support for one flavour of posix acls is detected, the corresponding module is statically linked into smbd (and active by default). So you by omitting vfs_solarisacl from the --with-shared-modules parameter in the configure command line and omitting the "vfs objects = solarisacl" line from smb.conf, you should have a working connection. I will provide a fix for the shared build soon. Cheers, Michael
Created attachment 3044 [details] Invalid. Attached find a patch agains 3.0.28. This also applies to 3.0.25, 3.0.26, ...
Comment on attachment 3044 [details] Invalid. Sorry, this got attached to the wrong bug report. (Why does commenting one bug drop me to the next bug in line....) This is not my day...
I wonder if this still applies to more recent samba versions as I have never seen this issue in my installations...
(In reply to Nils Goroll from comment #4) closing as I haven't seen this error in recent samba version either