similar to: [Announce] Samba 4.15.4 Available for Download

Release Announcements --------------------- This is the latest stable release of the Samba 4.20 release series. Changes since 4.20.6 -------------------- o? Vinit Agnihotri <vagnihot at redhat.com> ?? * BUG 15780: Increasing slowness of sharesec performance with high number of ???? registry shares. o? Ralph Boehme <slow at samba.org> ?? * BUG 15697: Compound rename from Mac

Release Announcements --------------------- This is the latest stable release of the Samba 4.20 release series. Changes since 4.20.6 -------------------- o? Vinit Agnihotri <vagnihot at redhat.com> ?? * BUG 15780: Increasing slowness of sharesec performance with high number of ???? registry shares. o? Ralph Boehme <slow at samba.org> ?? * BUG 15697: Compound rename from Mac

On 2020-03-30 14:33, Rowland penny via samba wrote: > It might help if you don't crop lines like the above from your logs, out > of context they are meaningless. > > If you are going to post log fragments, post the entire log fragment and > a few lines above and below it. Sorry. Here a full excerpt: > [2020/03/30 14:56:31.559263, 0]

Dear all, we updated to 4.12.10-10 using the sernet packages. After approx. 30 minutes I obtainted the following messages in syslog: root at ctdb-ho-2:~# journalctl -f -- Logs begin at Wed 2020-11-11 08:53:27 CET. -- Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: [2020/11/13 13:00:18.616823, 0] ../../source3/smbd/close.c:1150(close_directory) Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: close_directory:

Dear all, Following [1] from a year ago, I'd like to know what is the state of the crossrename VFS module, and whether it's expected to be supported at least together with the recycle module? To be honest I'm quite sympathetic with the reasoning in [1] and I don't see a general use of crossrename. However, it remains relevant in the context of recycle, and currently I

Hello. I'm seeing several of the above messages in my smbd logs. I see three different kinds: > close_directory: Could not delete share entry for . > close_directory: Could not delete share entry for {filename} > close_remove_share_mode: Could not delete share entry for file {filename} I could find no explanation on their meaning. Anyone has a pointer? bye & Thanks av.

Hi, I tried samba 4.12.0 on our file server which is a domain member and exporting some shares. We're getting some strange errors on some shares since the update. Right after starting or restarting smbd everything is fine. After short while (seconds or a few minutes) users are getting errors when trying to access the shares, e.q. "Invalid Handle Error", "An unexpected

Encountering a strange one... has been occuring since samba 4.15.x and continues to occur even in 4.17.5 and 4.18 Issue does not occur in earlier versions (4.13.x) and have switched back and forth between versions to confirm. Servers are winbind joined, PAM and krb5 auth, all seems to work fine (reading, writing, creating, moving) until trying to delete an empty folder on the share from Windows

On 10/03/2020 08:03, Andreas Hauffe via samba wrote: > We have a kerberized NFS4 running on that machine, too. I do hope that you are not resharing the NFS share(s) via Samba, that way lies madness ;-) Try this smb.conf: [global] ??????? workgroup = SUBDOM ??????? realm = SUBDOM.DOM.EXAMPLE.COM ??????? security = ADS ??????? bind interfaces only = Yes ??????? interfaces = lo enp1s0f0

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.2 -------------------- o? Douglas Bagnall <douglas.bagnall at catalyst.net.nz> ?? * BUG 15701: More possible replication loops against Azure AD. o? Ralph Boehme <slow at samba.org> ?? * BUG 15697: Compound rename from Mac clients can fail with ????

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.2 -------------------- o? Douglas Bagnall <douglas.bagnall at catalyst.net.nz> ?? * BUG 15701: More possible replication loops against Azure AD. o? Ralph Boehme <slow at samba.org> ?? * BUG 15697: Compound rename from Mac clients can fail with ????

On 2020-03-31 12:21, Rowland penny via samba wrote: > A 'share entry' is exactly that, a file or directory You mean, it's a client trying to delete a file/directory? From what I can see, crossing smbd's log and audit log, the message > [2020/03/30 15:23:16.754076, 0] ../../source3/smbd/close.c:1214(close_directory) > close_directory: Could not delete share entry

On Wed, Mar 15, 2023 at 04:53:16PM +0000, Rowland Penny via samba wrote: > > >On 15/03/2023 16:47, Jeremy Allison via samba wrote: >>On Wed, Mar 15, 2023 at 11:29:10AM -0400, CaptainTrips28 via samba wrote: >>>Encountering a strange one... has been occuring since samba 4.15.x and >>>continues to occur even in 4.17.5 and 4.18 >>> >>>Issue does not

Thanks, I will give that a try. But I need the 'winbind separator = +'. We use some expensive commercial software (e.g. ANSYS, ABAQUS, ...), which uses shell scripts to start their software under linux. These scripts are not able to handle a backslash in the user name. The only solution was to switch to a "+" character. We reported these issues two years ago. Regards,

Hi all, Is this something I should report in bugzilla? In my smb3.conf I have vfs object = recycle full_audit crossrename and when doing a classicupgrade, I'm getting a segmentation fault. It doesn't finish. (tried 4.1.2, 4.1.3, 4.1.4) When removing the line, the classicupgrade finishes successfully. It's easy to get around, but wouldn't it be nicer not to crash..?

Full_Name: Alessandro Usseglio V. Version: 1.5.0 OS: Linux RH 7.1 Submission from: (NULL) (130.60.71.55) Error during configure $ ./configure [...] checking for an ANSI C-conforming const... yes checking for int... yes checking size of int... 4 checking for long... yes checking size of long... 4 checking for long long... yes checking size of long long... 8 checking for long double... yes

Hi, we have a stange problem here since samba 4.12. Users on specific clients are not allowed to access a share after reboot of the client and in very rare cases suddenly during use. When we restart the smb service after the access denied message on the client for a share, the user is allowed to access the share. So there seems no problem with permissions. Are there any known reasons for

Hi guys I have a problem with Samba 4.0 shares covered by scannedonly VFS. Example configuration of one of those shares: path = /foo/bar/baz read only = No browseable = No vfs objects = scannedonly scannedonly:domain_socket = True scannedonly:socketname = /var/lib/scannedonly/scan scannedonly:hide_nonscanned_files = True scannedonly:allow_nonscanned_files = False Whenever I

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.1 -------------------- o? Ralph Boehme <slow at samba.org> ?? * BUG 15732: smbd fails to correctly check sharemode against OVERWRITE ???? dispositions. ?? * BUG 15754: Panic in close_directory. o? Pavel Filipensk? <pfilipensky at samba.org> ?? *

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.1 -------------------- o? Ralph Boehme <slow at samba.org> ?? * BUG 15732: smbd fails to correctly check sharemode against OVERWRITE ???? dispositions. ?? * BUG 15754: Panic in close_directory. o? Pavel Filipensk? <pfilipensky at samba.org> ?? *