Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Use cron to repair permissions on a regular basis' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Use cron to repair permissions on a regular basis
Authored by: tji on Nov 19, '04 01:37:40PM

I've seen quite a few tips on this site about repairing permissions. It seems like many people do this compulsively.

Why the need to do this so frequently? Are you guys concerned about security, and want to make sure the file permissions are locked down, or what?

[ Reply to This | # ]
repair permissions on a regular basis
Authored by: subscriber3 on Nov 19, '04 01:56:57PM

incorrect permissions can interfere with software installation, causing system and application problems.

[ Reply to This | # ]
repair permissions on a regular basis
Authored by: tji on Nov 20, '04 09:50:20PM

Yes, incorrect permissions can screw up many things. But, is there some reason to believe that the permissions are going to be constantly reset to incorrect values?

Why would one want/need to constantly do this?

In my 12+ years with Unix, and 2 years with MacOS X, I have not found this to be a major problem.

[ Reply to This | # ]
repair permissions on a regular basis
Authored by: werikblack on Nov 21, '04 01:17:06PM

The problem, though, is that if a developer has an installer or application that goofs up permissions, you're much more likely to see this on Mac OS X than you would on UNIX, IMHO. Consider the source of many of the applications you buy. With UNIX, you're typically buying from enterprise developers. On Mac OS X, there's a good chance you're buying apps from a 22-year-old developer sitting in his underwear coding for extra beer money. Definitely a difference in terms of bug checking.

[ Reply to This | # ]
Re: repair permissions on a regular basis
Authored by: Uncle Asad on Nov 22, '04 03:02:53PM

The Apple Installer / PackageMaker tools make it perhaps easier than it should be to create a package which will install and mess up permissions. It *looks* easy enough to create an installer package--hey, just fill in these fields!--but there are a lot of gotchas that aren't apparent through that esay interface. There are a number of good tutorials on the web outlining these gotchas, and Apple's documentation looks very thorough--but it seems so easy that many may not read the docs or search for the tutorials.

I've also had Backup once fubar the permissions on /tmp 2/3 of the way through a 7 CD backup and die, so applications (or perhaps OS bugs) can sometimes mess things up, too, but predominantly it seems to be poorly-created installer packages.

Bottom line, if you install software from vendors other than Apple, you should be running repair permissions--and running permissions before and after OS updates seems to help them work properly, too!

[ Reply to This | # ]