BakersT <> wrote:
> On 10.4.11 : I had been using 'Anacron' for a long time before seeing
> something to the effect that 10.4.8 included a change that would allow
> launchd to "catch up" to periodic scripts that didn't run because the
> system was down (or maybe just sleeping?) at the appointed time.
That would be consistent with my observations on 10.5 and later. If the
computer is sleeping when launchd is scheduled to run something, it
catches up after the computer wakes up.
launchd does not run anything which was missed due to the computer being
shut down at the scheduled time.
> I've removed Anacron, and "sudo launchctl list" shows that the
> daily/monthly/weekly scripts are scheduled, but they're not executing. Is
> that 'cuz my machine is normally powered-down (not just sleeping) when
> they're scheduled to run (default times, between 01:00 and 03:00 IIRC)?
Yes.
> Should I return to Anacron, or am I missing something? (And yes, I -do-
> want to power-down each evening, and I'd prefer not to have to remember to
> manually run the maintenance scripts.) Cheers...
Anacron would be one solution.
Personally, I'm perfectly happy to let my computers sleep overnight.
Modern Macs use very little power when asleep. They use less when shut
down, but it is still not zero.
--
David Empson