SliTaz Forum

CambsMart

Member

Registered: 2020-10-18

Posts: 7

Issue after upgrading Samba to 3.6.7

Running SliTaz 4.0 on a NAS server; recently added a Windows 10 client so require SMB3, so I've installed Samba 3.6.7 from the SliTaz 5.0 repository.

On trying to start Samba from the init.d Samba script, I get several errors from the script as follows

[c]root@slitaz:~# ../etc/init.d/samba restart
../etc/init.d/samba: line 12: _: not found
../etc/init.d/samba: line 12: _: not found
../etc/init.d/samba: line 71: _: not found
../etc/init.d/samba: line 71: action: not found
                                                                     [ OK ]
../etc/init.d/samba: line 12: _: not found
../etc/init.d/samba: line 71: action: not found
/usr/sbin/smbd: error while loading shared libraries: libgnutls.so.30: cannot open shared object file: No such file or directory
                                                                     [ OK ]
../etc/init.d/samba: line 71: action: not found
                                                                     [ OK ][/c]
The script should be the one from the 3.6.7 package, it's dated May 2016, although I didn't check the date on the previous version (3.5.8)

Any ideas why this doesn't start correctly?

mojo

Administrator

Registered: 2011-03-29

Posts: 2,173

Re: Issue after upgrading Samba to 3.6.7

Samba-4.1 is the first version that supports SMBv3

You could configure windows 10 to use SMBv1 client.

CambsMart

Member

Registered: 2020-10-18

Posts: 7

Re: Issue after upgrading Samba to 3.6.7

I could do that, but given that Samba 3.6.7.supports SMB3 I would rather do it the secure way.

CambsMart

Member

Registered: 2020-10-18

Posts: 7

Re: Issue after upgrading Samba to 3.6.7

Sorry, just spotted the 1st line of your reply (for some reason Firefox wasn't correctly displaying the threads yesterday). It appears that my man pages in my system are for the latest package versions, even if I don't have the latest packages installed; I don't know if they were updated when I installed the browser required to open them.

Looks like I can ignore the error I'm getting as 3.6.7 isn't any use to me!

CambsMart

Member

Registered: 2020-10-18

Posts: 7

Re: Issue after upgrading Samba to 3.6.7

So I've now installed the Samba 4.6.14 package from the 'next' repository and installed it, and I have exactly the same problem with the init.d/samba script; clearly the issue is with my environment, e.g I'm missing a command interpreter even though this is a shell script. Any ideas why the shell isn't correctly processing these lines:

[c]12   DESC="$(_ '%s server' Samba)"
71   esac[/c]

gibor

Moderator

Registered: 2011-04-30

Posts: 1,067

Re: Issue after upgrading Samba to 3.6.7

Do no mix packages of different repos, this broke dependecy on your installation.

The correct alternative is build directly from source code...

error reported was created of less function of tazpanel and busybox...