flowmac

Q: Problem with OS X file permissions on devices running other file system than "hfs"

Hi folks,

 

sorry for this detailed thread, but i tryed to gather all required information.

 

I am experiencing a total file / folder permission mess when i am using "rsync" to mirror folders from OS X to a NAS.

 

When i create a file test.rtf in OS X, the file premission looks like this:

8 -rw-r--r--    1 flo  staff   331  7 Mär 19:16 test.rtf

 

When i copy this file via finder to a OS X Extended (Journaled) formated firewire harddisc (hfs), the permission looks like:

8 -rw-r--r--   1 flo  staff   331  7 Mär 19:16 test.rtf

 

all cool.

 

When i copy this file via finder to a XFS formatted NAS (OS X interprets NAS's file system as a "smbfs"), the permission looks like:

2 -rwxrwxrwx  1 flo  staff    331  7 Mär 19:16 test.rtf*

 

super uncool.

 

Now using rsync:

rsync'ing the initial file test.rtf from OS X to OS X Extended (Journaled) formated firewire harddisc, the permission looks like:

 

...flo$ rsync -av file-permissions-test/ /Volumes/officeWD/file-permissions-test/

building file list ... done

./

test.rtf

 

sent 471 bytes  received 48 bytes  1038.00 bytes/sec

total size is 331  speedup is 0.64

 

8 -rw-r--r--   1 flo  staff   331  7 Mär 19:16 test.rtf

 

all cool.

 

rsyncing the initial file from OS X to to a XFS formatted NAS, the permission looks like:

 

2 -rwxrwxrwx  1 flo  staff    331  7 Mär 19:16 test.rtf*

 

super uncool. (at least rsync and the finder copy operation does the same)

 

I assume the changed rights / permissions has to do with how a drive is formatted (hfs, ntfs, ext3) etc.?

When i sync to a linux on ext3 it the same problem.

 

So, is this all about file system, and will this problem be solved using a Time Capsule (is this thing running hfs and can i access it via network?)?

thank you!

Posted on Mar 7, 2015 11:26 AM

Close

Q: Problem with OS X file permissions on devices running other file system than "hfs"

  • All replies
  • Helpful answers

Previous Page 2
  • by etresoft,

    etresoft etresoft Jul 28, 2015 1:39 PM in response to flowmac
    Level 7 (29,350 points)
    Mac OS X
    Jul 28, 2015 1:39 PM in response to flowmac

    Hello again flowmac,

    You have to remember that you are dealing with all kinds of different networking security mechanisms. The 777 actual refers to one specific mechanism that you aren't even using, NFS. Your Time Capsule uses AFP (AKA AppleTalk). Apple is now using Microsoft's SMB for any real client/server interactions. Just because it may appear to have 777 permissions on the server, and get reset to 777 after copying it back, does not mean that any user connected to said server can access the file.

     

    My Time Capsule died years ago so I'm unable to test this. When I try to copy files from a Yosemite VM to my Yosemite system, the permissions are unchanged. What are your configuration settings for the Time Capsule file server? Are you entering an account and password to access these files? If not, then you may be connecting as a Guest user. That would explain the 777.

     

    Even when my Time Capsule was still among the living, that was a few years ago. They may be using SMB now. This is a general "MacOS X Technologies" forum. I suggest you post your question in the Time Capsule forum instead: Time Capsule

  • by flowmac,

    flowmac flowmac Aug 3, 2015 9:48 AM in response to etresoft
    Level 1 (0 points)
    Aug 3, 2015 9:48 AM in response to etresoft

    Hi etresoft,

     

    thank you, I did open a thread over there.

     

    Yes, maybe since Yosemite turned to SMB3 they also changed something on the handling in AFP, i dunno. I logon to TC via username and password, so i expect that there is no 777 at all. It's strange, somehow.

Previous Page 2