Leopard Server & Permissions issues

Discussion in 'Mac OS X Server, Xserve, and Networking' started by bigandy, Jun 2, 2008.

  1. macrumors G3

    bigandy

    Joined:
    Apr 30, 2004
    Location:
    Murka
    #1
    I have an issue with a G5 Xserve running 10.5.2 Server.

    There are around 15 users with accounts connected to this particular box. All of them have an installation of Mac OS X 10.5.2 client, and use both Windows (via Parallels) and OS X to access files within the Public folder structure on the Server.

    It seems that permissions keep on changing once they're created. Sometimes seemingly randomly.

    How can I force the server to ensure that any files or folders created within the Public folder or subfolders are *always* created 777, rwxrwxrwx, or full access for all?
     
  2. macrumors member

    Joined:
    Jun 27, 2007
    #2
    I wouldn't recommend upgrading to OSX Server 10.5.x unless this problem is properly addressed by Apple. One solution could be creating a Folder Action or an Applescript, to propagate permissions.
     
  3. macrumors 6502a

    Sayer

    Joined:
    Jan 4, 2002
    Location:
    Austin, TX
    #3
    Assign all users to the same group, make that group owner of the root Public folder, use ACLs, train your users on how to use their computers to store files on a public share.

    Pick any two or three.

    Buy a SAN appliance.
     
  4. macrumors member

    Joined:
    Jun 27, 2007
    #4
    I'm curious, did anyone try osx server 10.5.3 yet? If so does it fix these problems?
     
  5. thread starter macrumors G3

    bigandy

    Joined:
    Apr 30, 2004
    Location:
    Murka
    #5
    It's on 10.5.2 at the moment, so that doesn't really help ;)

    I was thinking of doing that - but will it propagate to subfolders properly?

    I've never used folder actions - could I use them to run a shell script which recursively resets permissions, or could it catch the file that's been modified and alter that?

    Actually that group/ACL is in place on the Public folder currently. Why should the users do differently as they do now, which is creating documents and folders in the same way as they would a local file or folder? *mumbles to self, 'never had this issue with windows networks'* :rolleyes:

    It mentions permissions issues have been addressed, so I'll be updating before kicking off this evening... After a complete backup run, of course ;)
     

Share This Page