http://www.theronge.com/2005/07/13/symbolic-trouble/ Cocoa, Mac OS X and maybe a few other things. Wed, 20 Aug 2008 02:23:25 +0000 http://wordpress.org/?v=2.0.2 http://www.theronge.com/2005/07/13/symbolic-trouble/#comment-22279 Mon, 31 Mar 2008 15:03:25 +0000 http://www.theronge.com/2005/07/13/symbolic-trouble/#comment-22279 Symbolic links don't actually have access permissions of their own, they use the permissions of the entity that they point to. On some platforms, all symlinks are created 777 with root/0 ownerships regardless of who created them or what they point to, though if you tried to to write to a file pointed to by that symlink that you wouldn't have normal access to you would still get permission denied. This is a long way of saying, check the permissions of the canonical path name, to determine the permissions of the non-resolved path. Symbolic links don’t actually have access permissions of their own, they use the permissions of the entity that they point to. On some platforms, all symlinks are created 777 with root/0 ownerships regardless of who created them or what they point to, though if you tried to to write to a file pointed to by that symlink that you wouldn’t have normal access to you would still get permission denied. This is a long way of saying, check the permissions of the canonical path name, to determine the permissions of the non-resolved path.

]]> http://www.theronge.com/2005/07/13/symbolic-trouble/#comment-15487 Sun, 27 Jan 2008 11:18:55 +0000 http://www.theronge.com/2005/07/13/symbolic-trouble/#comment-15487 NSFileManager: - (NSDictionary *)fileAttributesAtPath:(NSString *)path traverseLink:(BOOL)flag with traverseLink:NO should do it for you. NSFileManager:
- (NSDictionary *)fileAttributesAtPath:(NSString *)path traverseLink:(BOOL)flag
with traverseLink:NO should do it for you.

]]>