Date: Thu, 12 Jul 2001 15:16:15 -0700 From: Tim Kientzle <kientzle@acm.org> To: keichii@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: misc/28920: periodic scripts do not run on desktop systems that aren't always on Message-ID: <3B4E21AF.1EEC97F8@acm.org> References: <200107121939.f6CJd1n00272@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
You're still assuming that there is a SINGLE TIME where the system is consistently on. This is clearly not always the case. Also, simply changing the cron job time is typically counter-productive, as some of the periodic jobs are quite hoggish. The system I've developed handles cron jobs that are run at odd times very carefully: * It runs the individual tasks with a lengthy delay between them so that the system isn't loaded with the full "monthly" or "weekly" suite, for example, while you're trying to get work done. (Jobs run at the "regular" late-night times are not run with an inter-job delay.) * The system runs jobs at the "regular" time with the regular priority. Jobs run at off times are niced. This system works very well for systems that are sometimes left on overnight and sometimes not. In that case, the periodic tasks get run late at night when the system is on, but still run occasionally if the system is not on at the preferred time. You're exactly right that an administrator can change the cron job times, but the system I've developed permits correct operation out-of-the-box with no need for such fine-tuning. It also handles a number of situations that the current periodic system does not handle at all. I would appreciate if you reconsider. As I mentioned in my original post, I do have complete source implementing this system if you'd like to take a more careful look at the basic concept. - Tim Kientzle keichii@FreeBSD.org wrote: > > Synopsis: periodic scripts do not run on desktop systems that aren't always on > > State-Changed-From-To: open->closed > State-Changed-By: keichii > State-Changed-When: Thu Jul 12 12:38:17 PDT 2001 > State-Changed-Why: > This is the user's administrative problem. > The user can change his cron job time as root. > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28920 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B4E21AF.1EEC97F8>