On Thu, Sep 01, 2022 at 09:06:07AM -0400, Tom Talpey wrote:
Ok, two things. What I found strange is the "man smb.conf.5ksmbd", and as you say that should be man 5k smb.conf. Sounds ok to me. But the second thing I'm concerned about is the reuse of the smb.conf filename. It's perfectly possible to install both Samba and ksmbd on a system, they can be configured to use different ports, listen on different interfaces, or any number of other deployment approaches. And, Samba provides MUCH more than an SMB server, and configures many other services in smb.conf. So I feel ksmbd should avoid such filename conflicts. To me, calling it "ksmbd.conf" is much more logical.
+1 from me. Having 2 conflicting file contents both wanting to be called smb.conf is a disaster waiting to happen. Please use ksmbd.conf.
