New comment by wangp on void-packages repository https://github.com/void-linux/void-packages/issues/27565#issuecomment-753409220 Comment: > It would be nice to determine which of these is responsible for the error. GIven that the complaint is about reading `secrets.tdb`, I would suspect `tdb-wrap` first. I moved `tdb-wrap` back to samba-libs. smbd starts up and appears to be operating correctly. ```diff diff --git a/common/shlibs b/common/shlibs index 26a6259f6d..38d371d881 100644 --- a/common/shlibs +++ b/common/shlibs @@ -4040,3 +4040,4 @@ libndr-samba4.so samba-libs-4.13.2_1 libsmb-transport-samba4.so samba-libs-4.13.2_1 libutil-cmdline-samba4.so samba-libs-4.13.2_1 libwinbind-client-samba4.so samba-libs-4.13.2_1 +libtdb-wrap-samba4.so samba-libs-4.13.2_1 diff --git a/srcpkgs/samba/template b/srcpkgs/samba/template index 646546a27b..f98df215a5 100644 --- a/srcpkgs/samba/template +++ b/srcpkgs/samba/template @@ -1,7 +1,7 @@ # Template file for 'samba' pkgname=samba version=4.13.2 -revision=3 +revision=4 build_style=waf3 build_helper="qemu" configure_script="buildtools/bin/waf" @@ -53,7 +53,7 @@ _privlibs="CHARSET3 MESSAGING_SEND MESSAGING LIBWBCLIENT_OLD addns ads \ printer_driver registry replace samba-cluster-support samba-debug \ samba-modules samba-security samba-sockets samba3-util samdb-common secrets3 \ server_id_db server-role samba_python smbclient-raw smbd_shim smbpasswdparser \ - socket-blocking sys_rw talloc_report_printf talloc_report tdb-wrap tevent-util \ + socket-blocking sys_rw talloc_report_printf talloc_report tevent-util \ time-basic torture trusts_util util_reg util_setid util_tdb ctdb-event-client" configure_args+=" --with-privatelibdir=/usr/lib --builtin-libraries=${_privlibs// /,}" @@ -174,7 +174,7 @@ samba-libs_package() { samba-credentials samba-errors samba-hostconfig samba-passdb samba-util samdb smbclient smbconf smbldap wbclient" _privlibs="cli-ldap cliauth common-auth dcerpc-samba gpo - ndr-samba ndr smb-transport util-cmdline winbind-client" + ndr-samba ndr smb-transport tdb-wrap util-cmdline winbind-client" for _lib in ${_libs}; do vmove "usr/lib/lib${_lib}.so.*" ``` > I repeat can someone post a smb.conf that is in use when smbd refuses to start. 'error code 13' usually is a permissions problem Here's one. It's basically just the default smb.conf, nothing special. ``` [global] workgroup = WORKGROUP server string = Samba Server server role = standalone server log file = /var/log/samba/%m.log max log size = 50 dns proxy = no [test-share] comment = test share path = /tmp/test-share guest ok = yes guest only = yes browseable = yes writable = yes printable = no create mask = 0664 directory mask = 2775 ```