qertafter.blogg.se - Batchmod permissions settings

#Batchmod permissions settings upgrade#
#Batchmod permissions settings full#
#Batchmod permissions settings software#
#Batchmod permissions settings free#
#Batchmod permissions settings mac#

Second, the only permission value that counts is the user permissions. If we knew what the permissions were before changing them and any error messages, it would be greatly helpful to diagnose this properly. It really ought to be enough to just open up the permissions to the file owner, not everyone else.įirst, I don't understand what the problem is. Personally, I think this "fix" is overcorrecting the original problem, and introducing new problems. the bug in the early iTunes updater that wiped out whole hard drives for some people), it would be the first one of this nature in several years. If you truly need wide-open permissions, that would seem to be an enormous bug on Apple's part, and while it wouldn't be the first time such a bug has made it into the wild (cf.

#Batchmod permissions settings full#

So, with that Unix arcana out of the way, back to the original proposal: is it *really* necessary to give wide-open permissions on *everything* in your iPhoto library to make the conversion to '11 work properly, or is it sufficient for the user to have full access? I suspect the safer permissions setting would be "664" permissions, or even "664", where the "6" means that the user (and maybe the group) has read/write access, the "4" means that others (and maybe the group) just has read-only access, and nobody has execute access. Or it might not, I haven't tried monkeying with it to find out, but there is that risk. In at least some cases, Apple uses custom ACLs to enforce "magic" behavior for certain files & folders, and it may be the case that deleting this information could have adverse effects with the iPhoto library.

Stripping out the ACLs may or may not be overkill.

You may regret that level of trust later.

#Batchmod permissions settings mac#

You want to give full read/write (and execute) permission to everyone? Surely it should be sufficient to just set this for the owner, and maaaaybe the group, but not everyone else, right? This may be splitting hairs, as the vast majority of Mac users have a single user account on the computer anyway, but if you have multiple users and, hypothetically, you do not 100% trust each other, then you're making it possible for any other user on the computer to access, modify, and delete anything in your iPhoto library.

Possibly harmless, but I can't see why it would be useful, and I can see scenarios where it would end up being a bad idea.

#Batchmod permissions settings software#

Photos & associated metadata files are not software programs, so it seems wrong to grant these files execute permissions, which is the bit that tells the system that it is valid to try to run these files as software programs.This is done recursively ("R") on all files under that folder, and it also strips out all ACL info ("N").Įxcept two or three big problems jump out at me here: Which is to say, give full read/write/execute permissions (that's what the "7" means) to the owner, group, and everyone else, for every file under your "iPhoto Library" folder. Wait, is that right? You're basically just running this command in an obtuse way: Finder in Snow Leopard has caught up, in my experience.] I am also a big fan of BatChmod there was a long time when it could be used to fix permissions when the Finder had problems doing so, especially recursive permissions. I upgraded to iPhoto 11 with no problems, but I did check my photo library and the permissions were already set as described in the hint. Be sure to have a current backup of your photo library prior to upgrading, as you should have a good data backup prior to any major software upgrade. [ crarko adds: There do seem to be a number of reports of this issue.

#Batchmod permissions settings upgrade#

This will set the photo library permissions so iPhoto 11 can do the necessary database upgrade without harm.

Also select the check mark for the following boxes: Change ownership and privileges, Clear ACLs, unlock box and Apply to enclosed folders and files.

Change the Letters R, W and X under the Owner, Group and Everyone to a check mark.

Drag and Drop your iPhoto Library (usually located in your ~/Pictures folder) into the open BatChmod window.

#Batchmod permissions settings free#

I first downloaded BatChmod, this is an excellent free utility.

If you have already lost data you will have to restore from Time Machine or whichever backup scheme you use.

While awaiting an official fix or advice from Apple, I have posted an easy, safe fix on my web site. Repairing permissions in Disk Utility won't help because that doesn't affect user files, only installed programs with Receipts. The root of the problem lies in faulty permissions within the iPhoto Library. Even more, some of the 'successful' upgraders are not even aware that they, might too, lost some files! A possible bug in the upgrade process by iLife 11 causes a loss in one's library.