View Single Post
  #11  
Old 09-28-2010, 12:09 PM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,923
Send a message via AIM to dnanian
OK. So, if you're getting prompted to run the script like this, there's something wrong with your system.

Here's the deal: we compile the script "driver" one time, when you schedule. That script is compiled so that it won't prompt on run - it's supposed to act like a regular program. And, as you previously indicated, that's how it acts most of the time.

We don't change anything, obviously, between runs. The schedule driver is exactly the same. But, you're getting different behavior - that is, the *system* is prompting when cron tries to run the schedule driver.

That shouldn't happen. The schedule driver hasn't changed (and as you've indicated previously, when you restart your Mac it often 'fixes' itself) and is not even *running* at that point. So - since the scheduler hasn't changed, and isn't running, the problem is with something *external* to the scheduler. Perhaps some maintenance tool you're running, or some other problem with your system.... but it's not the scheduler itself.
__________________
--Dave Nanian
Reply With Quote