This discussion is archived
4516 Views 7 Replies Latest reply: Jun 18, 2008 12:03 AM by Eric Guerin
Currently Being ModeratedMay 29, 2008 2:25 AM (in response to raydawg2000)I seems that we have the same problem. My problem is discussed here.
I hope the new Update will fix this issue.MacPro, Mac OS X (10.5)
Currently Being ModeratedMay 29, 2008 4:18 PM (in response to raydawg2000)try "sudo chown jamesl:FSUsers Web\ Development", or substitute a more appropriate user and group if you need to.
I'm guessing the problem is that you have the owner and group set to "root", which probably is not the best practice, and if you used any other owner or group the ACLs might be picked up. This can be viewed as a bug or a feature, personally I wouldn't want root-owned files or folders to be editable over any kind of file sharing, regardless of whether the ACLs said they could - so in my view the real problem is that any client can edit that file all all.
Are you sure the 10.5 client is connecting via SMB and not AFP? It could explain the difference.iMac, Mac OS X (10.5.3)
Currently Being ModeratedMay 29, 2008 7:37 PM (in response to Joseph Delaney)well this example is SUPER SUPER simplified. This is a filesever that is going to have a couple hundred users all split into about 30 or so groups. The files are owned by ROOT or the user who created them. Then permissions are handed out to others via the ACL's (users or groups). so its not as easy as just chown the files to whoever needs access.
and yes I am connecting via SMB and not AFP.
Currently Being ModeratedMay 31, 2008 9:48 PM (in response to raydawg2000)I've noticed this problem where Windows clients seem to ignore (or partially ignore) Mac OS X Server 10.5 ACLs, and only rely on the POSIX permissions. This problem isn't unique to Mac OS X Server; Mac OS X 10.5 exhibits the same behavior if you use ACLs on shared folders via SMB/CIFS.
However, I've found that making this adjustment solves the problem:
1. Stop SMB services using Server Admin.
2. Use nano or your favorite text editor to add the following text to the /etc/smb.conf file under the [global] section:
*acl check permissions = no*
3. Save the changes and start the SMB service again. Windows clients will need to reconnect; XP Home should reboot.
Here's my answer to a similar question, which you may find helpful: http://discussions.apple.com/thread.jspa?messageID=6997760�
--GerritApple Certified System Administrator, License to Apple via Sec. 2.10. of Terms; CC 3.0/Attribution to Everyone Else
Currently Being ModeratedJun 1, 2008 1:28 PM (in response to Gerrit DeWitt)thanks for the respnose.
but as I mentioned in my orignal post I already tried that command. Also not sure if it matters but the samba server isn't running on a MAC OSX server, its running on a redhat server. Every OS I have tried can connect to the server fine and the ACL's remain intact (including previous versions of OSX 10) except for OSX 10.5
Currently Being ModeratedJun 18, 2008 12:03 AM (in response to Gerrit DeWitt)Thanks for the response, but changing this setting:
acl check permissions = no
in the smb.config file did nothing for my situation.
I have a Mac 10.5.3 running Apache 2, when someone edits a .php, .html etc file on the Mac everything is fine. When someone connects to my machine using SMB File Sharing (Windows File Sharing) and opens up say a text editor like Dreamweaver to edit the file, and they save, the file is no longer readable from the Apache Server.
I have to use a utility called BatCHmod to clear the Leopard's Extra Permissions (ACLs). Each time I make a change over SMB this has to be done, it does not remember the previous permissions!
This is incredibly frustrating and did not occur prior to Mac OS X 10.5.3
Are there anyways to get the permissions permanently attached to the file, regardless of who is editing it and from what machine?iMac 20", Mac OS X (10.5.3), Did not occur prior to 10.5.3