From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Samba aborts on Raspberry Pi 3B
Date: Thu, 31 Dec 2020 04:56:36 +0100 [thread overview]
Message-ID: <20201231035636.3awCGs3thrXnDxBJ-Mlti7uzqwnRctOrPc0AamgA4rg@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: 1026 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/27565#issuecomment-752834714
Comment:
Unfortunately, I don't have any ARM hardware available for testing and only use a basic Samba configuration. If you can, please provide a bit more detail about the source of the problem:
1. Is it possible to disable the `idmap` configuration? If so, does the problem persist?
2. Can you temporarily remove an existing Samba password database and create a basic one with `smbpasswd`? Does that resolve the problem?
3. If you install the `-dbg` packages and try running `smbd` in a debugger, can you provide a stack trace at the panic?
If you are comfortable modifying the Samba template and rebuilding your own version, it would be helpful to know if native-built ARM packages suffer from the same problems. A last-ditch effort might be to disable the configuration options that build in many of the private libraries to see if there is unexpected breakage from these options.
next prev parent reply other threads:[~2020-12-31 3:56 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 [this message]
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
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=20201231035636.3awCGs3thrXnDxBJ-Mlti7uzqwnRctOrPc0AamgA4rg@z \
--to=ahesford@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).