Jon Buys wrote in letting me know of a little issue he’s having with the new Parental Controls feature of Leopard.
He writes in:
I enabled the Parental Controls on my new Leopard install, and after letting my kids play Frozen Bubble and browse to Playhouse Disney for an hour or so I found that the daemon named “
parentalcontrolsd” was eating 98-100% of one of my cores (Core 2 Duo MacBook).
Anyone else had this issue with the new Parental Controls? Have certain applications possibly caused the increase in CPU usage?