Register / Login | Desktop view |
Bruce Giles wrote:QRecall immediately attempts to run both the both the full backup and the home folder backup. I presume this is because some of the scheduled events occurred during the period that the Mac was off, and now QRecall is trying to catch up for the missed events.
If the event has already passed, I would prefer that QRecall just forget about it and wait for the next scheduled event. I could swear it used to work that way. Did I mis-remember, or did I do something wrong when setting up my scheduled tasks?
I thought that maybe "ignore while user is logged out" ... would do the trick, but it didn't.
I thought that maybe "ignore if no archive" ... would do the trick, but it didn't.
When the backups start running just after login, I usually cancel them from the monitor window. However, if I do that, and then reboot later, the backups attempt to run once again after login, even if another scheduled event hasn't yet occurred. Any ideas?
James Bucanek wrote:Bruce Giles wrote:If the event has already passed, I would prefer that QRecall just forget about it and wait for the next scheduled event. I could swear it used to work that way. Did I mis-remember, or did I do something wrong when setting up my scheduled tasks?
Bruce, you aren't mis-remembering. As one of QRecall's oldest customers, you probably remember when QRecall didn't run actions while the computer was asleep or shutdown. This generated a lot of complaints and the scheduler was modified to find, and immediately run, actions who's next scheduled time was now in the past.
Solution #1: If your system doesn't auto log into your account, you could set the scheduler to run as a daemon and add the "Ignore while user is logged out" option to your capture actions. The computer will start up, the scheduler will start, the actions will try to run, but won't because you're not logged in yet.
Solution #2: Add the "ignore if no archive" to your schedule. When you turn on your Mac, don't turn on your external drive. The scheduler will try to run the tardy actions, but see that there's no external drive and skip them. Once you're logged in, turn on your external drive and captures will begin normally.
When the backups start running just after login, I usually cancel them from the monitor window. However, if I do that, and then reboot later, the backups attempt to run once again after login, even if another scheduled event hasn't yet occurred. Any ideas?
That's hard to say. If four hours have passed, or you just logged out and four hours have past, I would expect the capture with the interval schedule to run immediately when you log back in. If the daily action is running immediately after being canceled, then something might be wrong. Start by sending a diagnostic report.
Finally, I'm considering adding an "ignore if asleep or shutdown" condition to actions in QRecall 2.0 so you can simulate the original behavior.
Bruce Giles wrote:So I saw you hint in another message that another beta cycle might be coming up soon. Care to comment any further on that yet?