Q: No more script activity

There's no way to answer your question since you don't explain how you're trying to scedule your script launches.

There are many ways to do it. Without knowing which one you're using it's impossible to guess what might be wrong.

Pardon me for putting it this way, but what are you talking about?  It's like you've started this conversation in the middle, and I have no idea what the context of it is. 

I mean, seriously: you don't want to schedule any scripts and don't need to either.  Does that mean your problem is solved, or is that your problem?  Or is that just background to some other problem that we're supposed to (but don't) already know?

And just for future reference, I don't really agree with you about the chipmunks.  They are an annoyance, but you can't really say they're a cause for concern.  Try leaving your sandwiches on the other side of the computer for a day or two; that should solve most everything.

The OP is referring to the Daily, Weekly and Monthly scripts. He had posted this same question in the Lion group a week or so ago Execution of maintenance scripts in Lion. Well at least there he started off at least describing what he was talking about

To the OP as long as my system is up it runs the scripts. If it is asleep when it is time for them to run then it runs them when it comes out of sleep. If the system is shutdown then you loose that cycle. It does not schedule them to run after a reboot.

If you're shutting down at night then change the scheduled time to when you have the system up.

regards

It is not lost if the system is asleep it will run when the system wakes. If the system is off the cycle is lost.

Again the scripts run on my systems with no modifications. if you're shutting down at night change the times the scripts run to when your system is up.

Mac OS X: About background maintenance tasks

from that page

In Mac OS X v10.6 and later, background maintenance tasks that do not run when the computer is asleep are run after it wakes from sleep mode.

Dub, that link you are pointing to refers to cron. cron is a unix utility for for running scripts on schedule - it is deprecated on OS X in favor of launchd, and may no longer be supported. 

Unless you've modified your system, maintenance tasks are run by launchd.  If they are not running as expected, then something has gone screwy with your system.  that's easy enough to check.  launch terminal, login to an administrator account, and type sudo launchctl list | grep periodic.  after you enter your password you should see:

Those indicate that the maintenance jobs are queued to run and ran correctly at last invocation.  If you don't see those, or see some number other than 0, post back.

if you're having trouble executing some different maintenance utility using cron, then you should convert it to launchd.

I don't know why it is so hard for you to understand how this works. People have been trying to explain it to you in both your old thread on this and in this thread.

If you want to ignore how this works, if you want to chase phantom problems fine have a good day.

launchd is generally verbose.  when it fails to do what it's supposed to do it reports it in console.  are you seeing any error messages from launchd related to the periodic tasks?