similar to: What does "vfs object = netatalk" really do?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [please cc to my address] Dear Samba and Netatalk experts, I've got a server running both samba 2.2.3a as PDC and netatalk (1.5pre7 as supplied by SuSE73). Samba machine accounts are added to /etc/passwd automatically by the command add user script = /usr/sbin/useradd -d /dev/null -g 90 -s /bin/false -M %u when a NT machine is added to the

hi list, i searched bugzilla but couldn't find an open/fixed bug for my problem: [system] - AMD Opteron 248, 8GB - SuSE 9.1 Prof. x86_64 - Samba v3.0.11-2.1 from ftp.samba.org (ftp://ftp.samba.org/pub/samba/Binary_Packages/SuSE/3.0/x86_64/9.1/) - netatalk v2.0.2 (self compiled) [situation] we're accessing our samba fileserver (files, directories, ... ) from different platforms

Hi all, Looking for a "best practices" way to share out to both Mac and PC easily. I know Windoze enables the same sharepoint for both the mac and pc shares and there don't seem to be any real "problems" by doing that. However I work in an environment which forces us to utilize Win9x through XP as well as OS 9 through 10.x on the mac side. I need a user friendly way to

I have a need to use the unsupported kernel for one feature only (AFP/Appletalk support). Never having had to use it before, I''m unsure of what''s all in it other than reading it''s config file. From those that do use it -- is it considered stable enough to use in lightweight production? I''m debating the use of it versus wasting my time rebuilding the normal

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 with samba and write them back in the new format? afp.conf: appledouble = ea ea = samba

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

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 =

Hi, I've got a SuSE 9.0 running Samba 3.0.1 and Netatalk 1.6.3 Samba is a member server of a win2k domain, I'm using winbind to authnticate my users. Well, with the Windows users, everything is ok. But not with the Mac users I'd like to setup Netatalk to authenticate my Macs against the win2k domain as with Windows. Is this possible? I've sarched the web all around and

Client: Dual 1GHz G4 OSX 10.2 Gig-Ethernet Server: Dual 2GHz P4 Linux 2.4.18 Raid-5 1TB Gig-Ethernet With netatalk 1.5.5 I get sustained writes of 66MB/s (yes, megabytes) With samba 2.2.7a I get sustained writes of 15MB/s I've tweaked the settings and ended up with these: socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 IPTOS_LOWDELAY SO_KEEPALIVE read raw =

(This is a brief announcement of a focused development/refinement of the Netatalk project.) The primary goal of Baltra is to provide a Mac OS X compatible AFP file sharing service with Samba 3.0 compatibility. We are hoping to have an AFP file sharing daemon which can run in parallel with Samba 3.0 to provide seemless file sharing amoungst SMB-based clients (Windows and MacOS-X) as well as

I guess I'm sort of surprised and I expected better performance I have a new server set up with RAID 10 drives (6) Repeated a number of times and though I am clumsy with stop watch timing, these numbers appear to be close enough for government work... Server, CentOS 5.2 and updated earlier today, just installed a week ago. Client, Macintosh G4, OS X 10.4.11 NFS Mount is done with the

Hi, We have about 2 dozen Mac OS9 computers running Dave 2.5.3 to access smb resources. Our print server, running Samba 2.2.7 (w/domain authentication), has no user accounts. PCs access the printers and print just fine, but the Macs using Dave get an authentication error of invalid user/password. They can access resources on the win2003 PDC. Any idea what's going on here specific to the

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

Why do you want TM to work over samba? Not sure it is supported completely by Apple although they did have developer documentation on it at one time: https://developer.apple.com/library/archive/releasenotes/NetworkingInternetWeb/Time_Machine_SMB_Spec/ I did see this on reddit, but have not tried it personally:

I have a Win2K Server that acts as a file server to a bunch of Macintosh machines on the network. Today I installed samba-3.0.5 on a Fedora1 machine, and mounted one of the server shares and tried to read it. Much to my surprise, I found files that are being listed like this: -rwxr-xr-x 1 root root 0 May 13 16:30 Icon?* -rwxr-xr-x 1 root root 25649 Aug 23 2000 webslide151.gif*

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

Hello, thanks in advance for the support! My samba server is samba-3.6.23-45.el6_9.x86_64, on Scientific Linux 6. Using a Mac it is possible to associate a color label to a file (suppose a word document). This can be done on the samba share too, but if I edit the file and save the changes the color label is lost (like if it is reset to empty). When the file is local or it is in shared volume

Take a look at this output from lsof: smbd 11490 0 8u REG 3,3 55296 1136647 Maintenanc.fp5 afpd 31010 0 2u REG 3,3 3207 1136655 auction - envelope.rtf afpd 31010 0 5u REG 3,3 4156 1136656 Word Work File L 1 afpd 31010 0 8u REG 3,3 55296 1136647 Maintenanc.fp5 smbd 31386 0 9u REG 3,3 4156 1136656 Word Work

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/ > writable = yes > vfs objects = catia fruit streams_xattr > fruit:locking = netatalk > fruit:encoding = native > streams_xattr:prefix = user.

Hey! I have been given the task to mirror our fileserver's filesystem onto a secondary machine for redundancy. The first thing that came to mind was rsync, but now I have few questions as I am far from an expert on this matter. Our file server is running Debian Stable. We use Samba for our Windows users and Netatalk (AFP) for our OS X clients. The filesystem used on the server is