similar to: FreeBSD, Libmd5, samba 4.9.4 & "smbclient -L" (using password) -> core dump

In my never-ending quest of removing clutter from the log files, I notice that we in /var/log/messages get a lot of: > Jul 25 13:08:30 filur00 winbindd[88603]: [2023/07/25 13:08:30.756462, 1] ../../source3/winbindd/winbindd_lookupname.c:122(winbindd_lookupname_recv) > Jul 25 13:08:30 filur00 winbindd[88603]: Could not convert SID S-0-0, error is NT_STATUS_NONE_MAPPED Seems to happen

We just noticed an interesting bug/misfeature on our Samba 4.9.4 servers (FreeBSD 11.2). The same effect is also visible on Samba 4.8.3 on CentOS 7. Start with a directory that looks like this: root at filur00:/tmp/test # ls -la total 50 drwxrwx--- 2 peter86 uf-iti-all 3 Feb 27 11:27 . drwxrwxrwt 10 root wheel 56 Feb 27 16:41 .. -rw-rw---- 1 mikha02 uf-iti-all 6 Feb 27 11:27

On Wed, 27 Feb 2019 16:53:48 +0100 Peter Eriksson via samba <samba at lists.samba.org> wrote: > We just noticed an interesting bug/misfeature on our Samba 4.9.4 > servers (FreeBSD 11.2). The same effect is also visible on Samba > 4.8.3 on CentOS 7. > > Start with a directory that looks like this: > > root at filur00:/tmp/test # ls -la > total 50 > drwxrwx--- 2

> Would this be on a DC ? > If so, you are removing the default vfs objects. and this is a known > ‘problem' Not on a DC - this is on AD member fileserver(s) It’s not a ‘problem’. It’s a _problem_. If you can’t add 'vfs objects’ without the default built-in module getting lost then how is that supposed to work at all? I’ve tried looking at the source code to see if there is

> hi all, > > my working samba-4.1.7 member of a samba3 domain (samba-3.5.3) failed > while updating to samba-4.2.0. Users were no longer able to access > shares because the trust account was broken. > > According to release notes (Winbindd/Netlogon improvements): > > For the client side we have the following new options: > "require strong key" (yes by

Hi, We are having issues with our samba server running on CentOS 7. It's generating core dumps and dumping them in the / (root filesystem) directory in the form of core.##### where the # is a series of numbers. Snippets of log files and some troubleshooting commands are below. Hope someone can have a look and see if I should file this as a bug, as there were similar posts in the samba

Hi, Hoping you can help. I've updated my samba server (PDC) from 3.0.10 to 3.0.14a as part of updating from FC3 to FC4. I now find I cant see inside any of the shares, even though I can see the share names themselves and the directories are quite readable to Linux processes. So, e.g. I can see that I have a share "Users", but not the contents of it. With one exception all shares