|
#1
| ||||
| ||||
| [HOWTO] - Keep permissions up to date automatically. The underlying BSD subsystem of Mac OS X, Darwin, uses a unix-style permissions system to determine who can see, access, search and execute files, folders and devices. Installer packages (.pkg and .mpgk) install software and puts files in various locations throughout your filesystem. The Installer also keeps receipts of these installations to facilitate keeping permissions up to date. Many, many, many seeminlgy random problems in OS X can be caused by permissions problems; repairing permissions is usually the first step recommended in troubleshooting a problem in OS X. Instead of waiting for a problem to crop up, why not set up your Mac to automatically repair permissions every night ? Here's how (you'll need administrator access) : 1. Open Terminal.app and type sudo pico -w /etc/crontab and enter your password. 2. You should see a file that has contents similar to this: Code: # /etc/crontab SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/var/log # #minute hour mday month wday who command # #*/5 * * * * root /usr/libexec/atrun # # Run daily/weekly/monthly jobs. 15 3 * * * root periodic daily 30 4 * * 6 root periodic weekly 30 5 1 * * root periodic monthly 10 * * * * root /sw/sbin/anacron -s Code: # /etc/crontab SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/var/log # #minute hour mday month wday who command # #*/5 * * * * root /usr/libexec/atrun # # Run daily/weekly/monthly jobs. 15 3 * * * root periodic daily 30 4 * * 6 root periodic weekly 30 5 1 * * root periodic monthly 10 * * * * root /sw/sbin/anacron -s # Repair Permissions, added by me. 0 1 * * * root /usr/sbin/diskutil repairPermissions / Alternatively you can use an application like CronniX, instead of the Terminal, to add the line to the system crontab.
__________________ michaelsanford.com Blog Twitter Tumblr LinkedIn iBook G4 1.42 GHz | MacOS X 10.5-current | 1 GB RAM, 100 GB HDD iMac G4 TFT 700 MHz | MacOS X 10.3.9 | 768 MB RAM, 40 GB HDD AMD Athlon64 3500+ | Slackware 12 (2.6.21.5-smp) | 2 GB RAM, 2120 GB RAID 1, 2500 GB RAID 0 |
|
#2
| |||
| |||
| Changing time for pre-defined scripts Thank you for the quick UNIX crontab primer. My next question would be, does changing the time values for the pre-defined daily/weekly/montly tasks here make them run at better times? I know there are lots of utilities to force run those tasks "now" but I wonder why no one has made such a utility to simply change when they are run automatically. I would think if it was as simple as editing the crontab file, it would have been integrated into Cocktail, etc. by now. Don
__________________ Don "Freiheit" Eitner Computer literate Mac newbie |
|
#3
| ||||
| ||||
| hmm you may be able to enhance performace by also putting in a line to use the command 'update_prebinding'
__________________ ON THE WAY: 15" PB 1.67|100|1024 --- 10.4 ------------------------------------------ 17" iMac G5 1.8|80|512|BT --- 10.3.9 FrankenMac G4 500|55|640 --- 10.3.9 PowerMac 9600 300|4|512 --- 1.2 eMachine 500is 500|4.3|196 --- OpenStep 4.2 Server 2.3|260|512 --- FedoraCore |
|
#4
| ||||
| ||||
| You might actually want to let anacron handle that - I notice you have anacron in your crontab. The point of anacron is that it can make sure scripts that run with a frequency of days or weeks (not multiple times a day) will be run, even if the computer is not on 24/7 - unlike cron, where if the computer isn't on at 1AM, the job is missed. Might even want to put periodic daily/weekly/monthly under anacron... see http://anacron.sourceforge.net/
__________________ What is the robbing of a bank compared to the founding of a bank? -- Bertold Brecht |
|
#5
| ||||
| ||||
| Hmm interesting...I love free software
__________________ ON THE WAY: 15" PB 1.67|100|1024 --- 10.4 ------------------------------------------ 17" iMac G5 1.8|80|512|BT --- 10.3.9 FrankenMac G4 500|55|640 --- 10.3.9 PowerMac 9600 300|4|512 --- 1.2 eMachine 500is 500|4.3|196 --- OpenStep 4.2 Server 2.3|260|512 --- FedoraCore |
|
#6
| ||||
| ||||
| One problem with this is that _if_ permissions are hosed, fixing them might not be enough to fix the problems one can have when they're 'unfixed': A reboot is often necessary... So: The cron (or anacron) job does its job, but you don't know whether there actually _were_ problems with permissions. I rather fix permissions once a week by hand - and if I see something weird come up in the process, I also reboot. Ceterum censeo that Apple should try and fix the problem of always having to fix permissions... *sigh*
__________________ MacBook Air 13" 1.6 GHz, 2 GB RAM, 80 GB HD. Mac OS X 10.5.4 MacBook 13" 1.83 GHz, 2 GB RAM, 160 GB HD. Mac OS X 10.5.4 Hackintosh Core2Duo 2.4 GHz, 2 GB RAM, 160 GB HD. Mac OS X 10.5.4 iPhone 16 GB, AppleTV 1G 40 GB (v2) Mac user since 1987, Apple Product Professional 2007, 2008. |
|
#7
| ||||
| ||||
| Fryke, WeeZer51402 and Apple should have a meeting ![]() WeeZer51402, you don't have to update prebinding in OS X 10.3 because fix_prebinding is called every time you launch an application and updates it if necessary. Fryke is right, Apple should fix this, maybe even in the style of fix_prebinding ! Adding it to the anaccrontab is a better idea, if you have a system that's not always on (like mine is).
__________________ michaelsanford.com Blog Twitter Tumblr LinkedIn iBook G4 1.42 GHz | MacOS X 10.5-current | 1 GB RAM, 100 GB HDD iMac G4 TFT 700 MHz | MacOS X 10.3.9 | 768 MB RAM, 40 GB HDD AMD Athlon64 3500+ | Slackware 12 (2.6.21.5-smp) | 2 GB RAM, 2120 GB RAID 1, 2500 GB RAID 0 |
|
#8
| ||||
| ||||
| So I've heard about the prebindings, has this changed since 10.2 or has it always been this way?
__________________ ON THE WAY: 15" PB 1.67|100|1024 --- 10.4 ------------------------------------------ 17" iMac G5 1.8|80|512|BT --- 10.3.9 FrankenMac G4 500|55|640 --- 10.3.9 PowerMac 9600 300|4|512 --- 1.2 eMachine 500is 500|4.3|196 --- OpenStep 4.2 Server 2.3|260|512 --- FedoraCore |
![]() |
| Thread Tools | |
|
|