|
|
10.4: One solution to a launchd-cron CPU usage issue
I believe I know what happened to the postee.
The QueueDirectories key in the plist tells launchd to monitor that folder and run cron whenever something is there. (Not just when something is created or updated, but if something exists.) So cron starts, looks in /var/cron/tabs and sees the .DS_Store file. It treats that file as a crontab but can't make sense of it and crashes. launchd does what it should and restarts cron.The cycle repeats and eats your CPU.
10.4: One solution to a launchd-cron CPU usage issue
Aha!! This might be what's happening to us. I'm a biologist with a fading memory of Unix administration from 10 years ago... I just set up a Tiger Xserve for our lab and everything was fine for a while and then the CPUs started maxing out at 100% due to cron activity! I suspect I may have the same problem as reported here. How in general can I avoid this in the future? I won't be using Finder to dig around in those folders, but if something does show up in that directory which causes cron to crash and be restarted, I'll have a problem again. How do people manage this issue? Is it really necessary for "cron to watch the /var/cron/tabs directory for new crontabs"? Can I turn that feature off, or is there a better/more elegant way to make sure this never happens? What should be in that directory, anyway? Currently, I see: |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.07 seconds |
|