Displaying 20 results from an estimated 5000 matches similar to: "setting up one share with multiple users - cannot edit files"
2015 Dec 29
2
vfs_fruit: cannot remove any file
Mon, 28 Dec 2015 18:24:17 +0100, Ralph Boehme <slow at samba.org>:
> On Tue, Dec 29, 2015 at 01:34:34AM +0900, HAT wrote:
>> In case of OS X 10.9 and later, any file could not be removed.
>>
>> $ rm test.txt
>> rm: test.txt: Resource busy
>>
>> cannot remove:
>> OS X 10.11.2 El Capitan
>> OS X 10.10.5 Yosemite
>> OS X 10.9.5
2017 Apr 03
0
Problem with Samba 4.5.8 as a macOS server
On Mon, Apr 03, 2017 at 03:46:49PM +0200, Frank Heldt via samba wrote:
> Hello all,
>
> I’m trying to use samba 4.5.8 as a file server for my Macs (all 10.12.4 now), as a replacement for netatalk.
>
> I did setup smb.conf as suggested
>
> #
> # Options for macOS
> # http://netatalk.sourceforge.net/wiki/index.php/Netatalk_3.1.11_SRPM_for_Fedora_and_CentOS
2015 Apr 25
0
vs_fruit - can't write to share
I must reply to my own post.
Changing the fruit:locking to "none" results in a working share.
Netatalk 3.1.6 is installed and from the information of the changelog Netatalk 3.1.7 doesn't change anything to the file locking (except if you're using Solaris).
Am 25. April 2015 bei 12:16:20, Christian Kovacic, MA (chris.k at gmx.at) schrieb:
Hi,
i'm running Samba 4.2.1
2018 May 13
0
move from netatalk to samba + vfsfruit
Am 13.05.2018 um 12:11 schrieb Reindl Harald via samba:
> since "ea = samba" was only added to very recent netatalk versions and
> so don't apply to files with a history of many years what is the way to
> go get rid of netatalk these days?
>
> is there still no tool to read/write the existing netatalk appladouble
> extended attributes which are *not* compatible
2015 Apr 25
2
vs_fruit - can't write to share
Hi,
i'm running Samba 4.2.1 compiled from source on an Ubuntu 10.04.4 LTS Server. ACL/XATTR is active and working. I tried to activate the vfs_fruite module and added the sample code:
vfs objects = catia fruit streams_xattr
fruit:resource = file
fruit:metadata = netatalk
fruit:locking = netatalk
fruit:encoding = native
to the share. In addition i tried the following share definition:
vfs
2015 Dec 26
1
vfs_fruit: xattr imcompatible with netatalk
On 26/12/15 17:33, HAT wrote:
> Sat, 26 Dec 2015 17:22:56 +0000, Rowland penny <rpenny at samba.org>:
>> On 26/12/15 17:08, HAT wrote:
>>> Hi,
>>> I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide.
>>>
>>> The EAs are not seen from clients yet.
>>>
>>> smb.conf:
>>> path = /export/test1/
>>>
2015 Dec 21
1
Fruit module configured to use matter still write ._* files
I have configured samba as follow:
[global]
workgroup = GOYMAN
netbios name = MATRIX
security = user
encrypt passwords = yes
smb passwd file = /var/db/samba4/private/passdb.ntdb
vfs objects = catia fruit streams_xattr
fruit:resource = xattr
fruit:metadata = netatalk
fruit:locking = netatalk
fruit:encoding = private
[projects]
path = /data/projects
write list = kuon, ino
force create mode = 0770
2016 Jan 09
2
vfs_fruit: FreeBSD: attrname is wrong
In case of FreeBSD, the name of the extended attribute is wrong.
% lsextattr user ICONandEA.txt
ICONandEA.txt netatalk.Metadata com.apple.TextEncoding com.apple.metadata:kMDItemFinderComment
"netatalk.Metadata" is incompatible to Netatalk.
The first atom "org." is removed.
source3/include/smb.h:
/* Prefix for DosStreams in the vfs_streams_xattr module */
#define
2017 Apr 03
3
Problem with Samba 4.5.8 as a macOS server
Hello all,
I’m trying to use samba 4.5.8 as a file server for my Macs (all 10.12.4 now), as a replacement for netatalk.
I did setup smb.conf as suggested
#
# Options for macOS
# http://netatalk.sourceforge.net/wiki/index.php/Netatalk_3.1.11_SRPM_for_Fedora_and_CentOS <http://netatalk.sourceforge.net/wiki/index.php/Netatalk_3.1.11_SRPM_for_Fedora_and_CentOS>
#
ea support = yes
vfs
2016 Jun 09
0
Samba 4.2 - OS X 10.11 - permissions are being ignored
On Thu, Jun 09, 2016 at 02:11:15PM +0200, Martin Markert wrote:
> Hi,
> when saving a file to this share the permissions (0777) are being
> ignored under OS X 10.11.5. All files will get these permissions:
> 0755. I don't know why?
Remember, "force XXX mode" only applies to file/directory
creation. The client is then free to change permissions
after the object is
2020 May 29
3
Extended attributes not working on mac
I worked with Netatalk for years and want to switch to Samba now. Currently i use Ubuntu 20.04. and Debian 9 before, i had no issues with netatalk at all.
As soon as i try to add a color tag (e.g. yellow) with Mac OS 10.15.5, the tag appears shortly but hides one second later. The file system is ZFS with no special options configured.
I tried the Ubuntu package but also the builds from source
2016 Oct 10
0
Mac OS Timemachine over SMB
Hello Kevin,
Mac OS by default looks for TimeMachine volumes over AFP not CIFS-SMB… Like you, I experimented with Samba a couple of years ago to try to get it to work anyway.
With a few modifications on the client’s part and some configuration on the Samba server I got it to work… but recovery only worked for clients that I had configured in advance… Recovery with the Mac OS tools (Migration
2015 Dec 17
2
vfs_fruit: xattr imcompatible with netatalk
On Fri, Dec 18, 2015 at 02:20:54AM +0900, HAT wrote:
> Thu, 17 Dec 2015 18:05:33 +0100, Ralph Boehme <rb at sernet.de>:
> > iirc you need fruit:encoding = native
>
> Solved. Thanks!
> I'm looking forward to netatalk 3.1.8.
>
> $ getfattr Mew.txt
> # file: Mew.txt
> user.com.apple.TextEncoding
> user.com.apple.metadata:kMDItemFinderComment
>
>
2015 Mar 11
0
vfs_fruit: xattr imcompatible with netatalk
Hi HAT!
Nice to meet you over here... ;)
On Wed, Mar 11, 2015 at 11:30:45PM +0900, HAT wrote:
> Hi.
> I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha.
> I confirmed that ResourceFork and FinderInfo are compatible with
> Netatalk 3.1.7. However, EAs are incompatible.
> The character ":" in EA name is wrong.
> The EAs are not seen from clients.
>
2016 Jun 09
6
Samba 4.2 - OS X 10.11 - permissions are being ignored
Hi,
when saving a file to this share the permissions (0777) are being
ignored under OS X 10.11.5. All files will get these permissions: 0755.
I don't know why?
Samaba Version 4.2.7-SerNet-RedHat-19.el6
CentOS release 6.7
[global]
workgroup = BAVARIA
server string = Samba Server %m
netbios name = NASBAV1
log file = /var/log/samba/%m_%a_%R.log
2020 Oct 20
0
File copy with macOS Finder leaves random files grayed out using vfs_fruit
Hi all,
We use the vfs_fruit module and lately we have experienced that random files copied with Finder are being grayed out. We think this is probably due to the extended attribute "user.DosStream.AFP_AfpInfo:$DATA" not being updated/removed after the file is copied. If we manually remove the xattr in question with the command setfattr -d 'user.DosStream.AFP_AfpInfo:$DATA', the
2016 Jun 13
2
Samba 4.2 - OS X 10.11 - permissions are being ignored
Am 2016-06-09 18:16, schrieb Jeremy Allison:
> On Thu, Jun 09, 2016 at 02:11:15PM +0200, Martin Markert wrote:
>> Hi,
>> when saving a file to this share the permissions (0777) are being
>> ignored under OS X 10.11.5. All files will get these permissions:
>> 0755. I don't know why?
>
> Remember, "force XXX mode" only applies to file/directory
>
2017 Nov 05
0
Error copying files with extended attributes to Windows clients
I just upgraded to 4.7.1 to fix an unrelated bug with deleting
directories for OS X clients, and it looks like this bug has been fixed
too. I re-enabled ea support, and copies work. It does look like some
attrs are lost in the process, but that's probably because they are
larger than some NTFS limit?
getfattr vlc-2.2.2.dmg
# file: vlc-2.2.2.dmg
user.com.apple.diskimages.fsck
2015 Mar 11
4
vfs_fruit: xattr imcompatible with netatalk
Hi.
I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha.
I confirmed that ResourceFork and FinderInfo are compatible with
Netatalk 3.1.7. However, EAs are incompatible.
The character ":" in EA name is wrong.
The EAs are not seen from clients.
smb.conf:
[test2]
path = /export/test2
writable = yes
vfs objects = catia fruit streams_xattr
fruit:locking =
2020 Apr 07
1
issues with Time Machine - did macOS change how they handle things?
TL;DR: Time Machine cannot create a *new* backup on my shared drive, but can add to an *existing* backup.
I'm running macOS Catalina and my Time Machine backs up to a Debian 10 server with NetAtalk and Avahi. Since Mavericks macOS has preferred SMB, and given SMB is marginally faster I decided to switch to using SMB for the Time Machine shares. On a fresh AFP share I can start a new Time