[Samba] Samba's winbindd is running but seems non-functional.
zombie_ryushu at yahoo.com
Mon Jun 20 03:01:57 UTC 2022
On 6/19/22 22:57, Andrew Bartlett wrote:
> On Sun, 2022-06-19 at 20:30 -0400, Zombie Ryushu via samba wrote:
>> The UNIX pipe over which clients communicate with the |winbindd|
>> program. For security reasons, the winbind client will only attempt
>> to connect to the winbindd daemon if both the |/tmp/.winbindd|
>> directory and |/tmp/.winbindd/pipe| file are owned by root.
>> I noticed that I do not have the /tmp/.winbindd/pipe file. What controls
>> it's creation? I do have the
> I spent far more than was warranted to fix this properly for Samba
> 4.17. The docs are old and out of date, we don't use /tmp/.winbindd
> any more.
> Note that if you are running Samba as an AD DC, winbindd is started
> internally by Samba, and should not be started by the system as well.
> Perhaps again work to ensure your system is as simple as possible.
> But also please just stop, then really stop and finally think about
> what might be different about your system compared to all the others
> that do 'just work' with Samba.
> Remove complexity. Perhaps set up a test environment that you can
> compare with - so you don't keep jumping at shadows - where you can see
> it does just work despite various errors in the docs.
> Finally, reopening old bugs isn't a good move to keep us helping you,
> so don't do that. If this thread (or worse, a mail stream) explodes
> like your many previous discussions then the Samba Team will not
> hesitate to put your posts under moderation.
> Andrew Bartlett
I have, I completely re-did everything, and removed all my extra stuff
including my shares.
It's still the same problem, Bind DLZ or Samba Internal makes no difference,
More information about the samba