Hi Pete, Thanks for the suggestions.
FWIW I've been running the fruit extensions and a few other tweaks for quite a while. My current global configuration contains: vfs objects = catia fruit streams_xattr zfsacl fruit:resource = xattr fruit:locking = netatalk fruit:time machine = yes #dflt: fruit:resource = file #dflt: fruit:locking = none fruit:advertise_fullsync = yes nfs4:mode = special nfs4:acedup = merge nfs4:chown = yes # could be derived from this article: # https://blogs.oracle.com/marks/entry/zfs_acls mangled names = no hide dot files = no # prevent created files having execute bit set? map archive = no # prevent SMB1, which seems to be bad: # https://www.cyberciti.biz/faq/how-to-configure-samba-to-use-smbv2-and-disable-smbv1-on-linux-or-unix/ min protocol = SMB2 # Seems to be required for Spotlight (tracker) support (see spotlight = yes on shares, below) # see: https://wiki.samba.org/index.php/Spotlight rpc_server:mdssd = fork rpc_server:mdssvc = external socket options = IPTOS_LOWDELAY TCP_NODELAY browseable = yes No, I haven't actually got Spotlight to work on the samba shares. Any hints on that front would be appreciated. The documentation on some of those Gnome-desktop background things is possibly worse than the Apple documentation... I find that quite a lot about modern computing resembles magical thinking, or occult practices: there is almost no way to actually understand what is going on, you just try things and stick to what seems to work. Superstition over science. Sigh. I can't remember why I'm not using fruit:encoding = private, but I think that it was because I wanted file names to be representable and compatible on both sides of the share, at the expense of occasionally having to "fix" names that turn out to be unrepresentable. I've bumped log level up to 2 and increased the size of the log files by a factor of ten (to 5000 (k)). I suspect that one reason why I wasn't seeing errors being reported could be that the logs were being turned over too quickly. We'll see. Cheers, Andrew Reilly E: arei...@bigpond.net.au M: +61-409-824-272 > On 24 Nov 2019, at 22:15, Pete French <petefre...@ingresso.co.uk> wrote: > > I have a very similar setup to you for serving files to my Mac from a FreeBSD > server. I haven't seen the unmount problem, but I di have a few oddities > until I added the 'fruit' module on the Samba side, which helps with > compatbiloty with the Mac. The appropriate bit of my config looks like this: > > vfs objects = fruit streams_xattr zfsacl > fruit:resource = xattr > fruit:encoding = private > > Don't ask me what they do anymore, I added them ages ago, but it does work > very nicely for me. You may already have this of course, but worth pointing > out just in case as it took me a few years to discover it! > > As someone else has said though, this may well be a Catalina bug. I am not > running that (MacBook too old, and not buying another until the new keyboards > are avilable n the replacement I want). > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
