samba - Oct 2019 - Subject=Re: Mac Clients Disconnect with: source3/smbd/service.c:1050(close_cnum) closed connection to service data

(example: Configure Samba to Work Better with Mac OS X [
https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X]
).

Thanks for the suggestion though.

I've now been trying out the various Apple specific flags in vfs_fruit (
https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html), though
with no success thus far.

Example settings tried in smb.conf:

[global]

min protocol = SMB2

inherit permissions = yes

fruit:advertise_fullsync = true

fruit:aapl = yes

fruit:resource = xattr

[data]

durable handles = yes

kernel oplocks = no

kernel share modes = no

posix locking = no

spotlight = yes

vfs objects = catia fruit streams_xattr


-- 
Louis Waweru
Senior Staff Associate
Department of Psychology
373 Schermerhorn Ext.
Columbia University
(212) 854-8167
(347) 843-9167

I notice the Configure Samba to Work Better with Mac OS X has been radically
shortened?not sure why, but you may want to look at my original 22 Apr 2019
version in the history.
You may want to put vfs objects in Global. Note in the vfs_fruit man page: Be
careful when mixing shares with and without vfs_fruit. OS X clients negotiate
SMB2 AAPL protocol extensions on the first tcon, so mixing shares with and
without fruit will globally disable AAPL if the first tcon is without fruit.
Is fruit:advertise_fullsynce a legal parameter?  I don?t see it in the vfs_fruit
man page.
 
inherit permissions should be Share

Torch
> On 28Oct 2019, at 21:07, Louis Waweru <law2175 at columbia.edu>
wrote:
> 
> (example: Configure Samba to Work Better with Mac OS X
[https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X]
<https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X%5D>).
> 
> Thanks for the suggestion though.
> 
> I've now been trying out the various Apple specific flags in vfs_fruit
(https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html
<https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html>),
though with no success thus far.
> 
> Example settings tried in smb.conf:
> 
> [global]
> min protocol = SMB2
> inherit permissions = yes
> fruit:advertise_fullsync = true
> fruit:aapl = yes
> fruit:resource = xattr
> 
> [data]
> durable handles = yes
> kernel oplocks = no
> kernel share modes = no
> posix locking = no
> spotlight = yes
> vfs objects = catia fruit streams_xattr
> 
> 
> -- 
> Louis Waweru
> Senior Staff Associate
> Department of Psychology
> 373 Schermerhorn Ext.
> Columbia University
> (212) 854-8167
> (347) 843-9167

On 29/10/2019 13:17, torch via samba wrote:
> I notice the Configure Samba to Work Better with Mac OS X has been
radically shortened?not sure why, but you may want to look at my original 22 Apr
2019 version in the history.
> You may want to put vfs objects in Global. Note in the vfs_fruit man page:
Be careful when mixing shares with and without vfs_fruit. OS X clients negotiate
SMB2 AAPL protocol extensions on the first tcon, so mixing shares with and
without fruit will globally disable AAPL if the first tcon is without fruit.
> Is fruit:advertise_fullsynce a legal parameter?  I don?t see it in the
vfs_fruit man page.
>   
> inherit permissions should be Share
>
> Torch
>
When the wiki page was created, I examined it and thought a lot of the 
given lines were actually default lines, but I left them in because I 
didn't want to put the author off. The page has now been updated by the 
Samba team member that writes most of the code required for MAC 
machines, so I am very sure that anyone trying to get Samba to work 
nicely with a MAC, should follow the latest wiki page: 
https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X

:-)

Rowland