Date: Mon, 17 Sep 2007 11:30:58 -0400 From: Bill Moran <wmoran@potentialtech.com> To: "Steve Franks" <stevefranks@ieee.org> Cc: User Questions <freebsd-questions@freebsd.org> Subject: Re: cron jobs not done during sleep Message-ID: <20070917113058.a85fec74.wmoran@potentialtech.com> In-Reply-To: <539c60b90709170822yedd52e0mcc9c8a5ff8ed0932@mail.gmail.com> References: <539c60b90709170822yedd52e0mcc9c8a5ff8ed0932@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to "Steve Franks" <stevefranks@ieee.org>: > Correct me if I'm wrong, but cron doesn't keep track of the last time > something was done, does it? Which is to say if my system is crashed, > was asleep, or powered off when a job is supposed to happen, it will > not happen the next time the system is successfully operational, will > it? It's not obvious to me for sure either way from any sources I've > read (man crontab, google), and unix tends towards k.i.s.s. (which is > why we like it) > > ...I understand why that would be important behavior if something > would cause problems executed other than 9am on Mondays... > > Is there a tool or setting to implement this functionality? I want > something to happen weekly, I don't care when. Assume I am off the > commercial power grid and I'm not going to leave my system powered on > just to make sure my backups get run. I use it when I need it, then I > turn it off. More people should. Electricity is not free from a > economic, social, or environmental perspective, and promises to be > less so with time. BSD's cron doesn't have this functionality. The Linux folks have a cron-ish program that does recognize when jobs have been missed and runs them at the earliest opportunity. I dislike it, personally, but I can see where it's convenient in some circumstances. http://anacron.sourceforge.net/ It's in ports. -- Bill Moran http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070917113058.a85fec74.wmoran>