From: wangp <wangp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Samba aborts on Raspberry Pi 3B
Date: Sat, 02 Jan 2021 01:28:13 +0100 [thread overview]
Message-ID: <20210102002813.Is9qWOBjZhM2SC5a7N3pfcaVf_hI6Pk2q9e8qh6jI_Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27565@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2850 bytes --]
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
```
next prev parent reply other threads:[~2021-01-02 0:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 0:01 [ISSUE] " wangp
2020-12-31 3:56 ` ahesford
2020-12-31 5:39 ` ericonr
2020-12-31 14:10 ` Anachron
2020-12-31 14:11 ` Anachron
2020-12-31 15:56 ` ahesford
2020-12-31 17:18 ` hortimech
2020-12-31 17:44 ` ahesford
2021-01-01 7:54 ` wangp
2021-01-01 7:57 ` wangp
2021-01-01 13:53 ` Anachron
2021-01-01 13:58 ` ahesford
2021-01-01 14:03 ` hortimech
2021-01-01 14:15 ` Anachron
2021-01-01 14:27 ` ahesford
2021-01-01 18:30 ` Anachron
2021-01-01 18:40 ` hortimech
2021-01-02 0:28 ` wangp [this message]
2021-01-02 0:41 ` ericonr
2021-01-02 0:42 ` ericonr
2021-01-02 11:12 ` andry-dev
2021-01-02 13:12 ` wangp
2021-01-02 19:06 ` ahesford
2021-01-05 3:42 ` [ISSUE] [CLOSED] " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210102002813.Is9qWOBjZhM2SC5a7N3pfcaVf_hI6Pk2q9e8qh6jI_Y@z \
--to=wangp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).