What this article doesn't mention is the horrendous problems with Lion Server. Permissions (via Get Info) that you can set, but that magically don't get set for

What this article doesn't mention is the horrendous problems with Lion Server. Permissions (via Get Info) that you can set, but that magically don't get set for no apparent reason. Server app that can't do something so simple as assign users to groups (Poof, your assignments are gone. No reason, no explanation). SMBX is a steamy pile of sh!t that is nearly unusable. It constantly drops Windows clients for no apparent reason. Didn't save? Tough cookies. It renders many applications unusable that worked fine in Samba. It retains file locks, so that after you close a document you can't open it again. I abandoned SMBX and compiled Samba 3.6.0 It's stable. Doesn't drop connections. No retained file locks. The apps that SMBX broke run again. But it also ignores Mac ACLs. Only recognizes Posix permissions, so this comes with its own set of problems. There's no way to force AFP to use a particular umask when creating files, and by default, Mac clients have a umask of 022, so even if you enable set-GID to force a group assignment, you can't force group permissions without re-configuring every Mac on the network to use a umask of 002. Very painful. The only redeeming thing about this whole experience is that we have a blazingly fast Thunderbolt RAID array (something that is only possible on Lion unless you really want to use a Macbook Pro as a server). If you ignore their Server app, use Workgroup Administrator instead, and set all permissions from the command line, AFP works like a dream. And for those who would say, "Why don't you use Linux then?" We used to. Both Netatalk and Samba get horribly slow when you are working with very large file systems. Netatalk because the CNID DB gets unwieldy, and Samba because of problems running case-insensitive sharing on a case-sensitive filesystem.