Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Why excessive authentication on moving files/folders?

Nov 4, 2011 3:31AM PDT

I am rebuilding the main HD in my Mac Pro (OS 10.6.Cool from the bottom up. I like to keep my Applications and Utilities folders tidy - all communications-related applications in a Communications subfolder, all back-up utilities in a Backup folder etc. One or two applications and utilities don't like that but I know about those and let them be. I also have my own definition of what distinguishes an application from a utility - if it produces a product separate from itself (Word, Toast etc.) it's an application, if not it's a utility. There are also some cases where this schema does not work but overall this configuration has served me well for many years and Systems up to and including Snow Leopard. I have erased the HD, installed/updated the system and am now at the stage where I begin to impose order on the applications and utilities bundled with the System. This time I find that every move I make, however trivial, needs authentication. This never happened before and has the potential to slow up the rebuild considerably. A potential solution on the MacRumours site <http://tinyurl.com/6c45jmr> had no effect. Any ideas about causes or - even better - solutions?

Discussion is locked

- Collapse -
Clarification Request
(NT) Repairing permissions has no effect?
Nov 4, 2011 5:08AM PDT
- Collapse -
Why excessive authentication on moving files/folders?
Nov 7, 2011 12:42AM PST

No - tried that early on but it made no difference.
F

- Collapse -
Clarification Request
look for Apple Support threads about "ACLs"--since 10.5
Nov 7, 2011 1:12AM PST

big recurring problem; lots of partial fixes that work for a while for some people; never explained well anywhere. Searching at Apple's Support will find literally dozens of threads about this problem since OSX 10.5