You can only repair permissions on the boot partition.
The command is: diskutil repairPermissions /
What I did was implement the following on my initial system image
I changed the "daily.local" to "weekly.local" since I didn't want to run it
every day.
You can create a generic daily.local file on your system then push it to the
other systems using ARD.
taken from http://www.macosxhints.com/article.php?story=20030120061404240
================================================
Run Repair Permissions Automatically On A Schedule In the Background Late at
Night, Elegantly
Authored by: Lectrick on Thu, Jun 5 '03 at 07:39PM
A more elegant way to do this is to create a daily.local script in /etc/
with the single line of "diskutil repairPermissions /"
cd /etc/
sudo pico daily.local
diskutil repairPermissions /
control-O to save out, hit enter
control-X to exit
sudo chmod +x daily.local
You're done!
This file is then called by the "daily" script which is already run by the
default OS X installation, every night at 3:30AM (which you can see if you
use Cronnix- if you pick the menu command "Open System Crontab" you will see
"periodic daily/periodic weekly/periodic monthly" which are just ways to
execute maintenance scripts.)
The other nice thing is that a new OS X install (as long as you install
over your existing install) likely won't obliterate this file. (if you want,
you can probably make a non-root-user copy of this file in your home
directory somewhere as a backup)
on 6/10/04 11:21 AM, Rich Trouton at email@hidden wrote:
> Is there a way to shell-script permissions repair without knowing the
> disk's BSD name in advance, wrap it in a script-only package, then use
> ARD to push the package over the network? There shouldn't be a problem
> with the packaging once I have the script, but I'm not sure where to
> begin with the script after having looked at the diskutil command. It
> looks like it wants a specific ID for the drive and I'm curious to know
> if anybody's run into, and fixed, this problem.
>
> For example, when I take a look at the boot partition (I have a 250GB
> drive with three partitions) on my desktop Mac through Apple System
> Profiler, it shows up as disk0 for the BSD name. On my PowerBook, where
> I have one partition set up, the drive shows up as disk0s9. Does this
> matter to the the diskutil command, or can I tell it to just look for
> the active boot partition and fix the permissions on that?
>
> Thanks,
> Rich
>
> ---
>
> Rich Trouton (Contractor)
> LAN Support
> email@hidden
> -----------------------------------------------------------
> National Human Genome Research Institute
> National Institutes of Health Bethesda, MD
>
> The best way to get in touch with me is through email.
> _______________________________________________
> remote-desktop mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/remote-desktop
> Do not post admin requests to the list. They will be ignored.
-------------------------------------------------
Michael Kern
IT Specialist
Center for Bioethics - University of Pennsylvania
3401 Market Street - Suite 320
Philadelphia 19104-3308
Phone: (215) 573-5059
Fax: (215) 573-3036
_______________________________________________
remote-desktop mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/remote-desktop
Do not post admin requests to the list. They will be ignored.
