Kevin, On Wednesday 28 June 2006 05:13, Kevin Donnelly wrote:
On Tuesday 27 June 2006 22:43, Carlos E. R. wrote:
Well, the thing is, cron is designed for systems that stay continuously on, but that is not the case for most home users (and business users should power off their computers when not used for the environment sake).
I can see the rationale, but it doesn't hold water. If the system is not on continuously, it is inherently less likely that the tasks need to be run every 24 hours, so why not let the user choose when he/she wants to run them?
That argument is the thing that does not "hold water." The number of hours per day that the system runs does not affect its need to run periodic maintenance and / or diagnostic tasks. And in fact, the system is adaptive and when it finds that it has not run the tasks on schedule, it runs them when it can. Unfortunately, for systems that are only powered on when used, this has a strong tendency to cause the periodic tasks to interfere with the use for which the machine was powered on. I agree that it should be possible for the end user to specify when daily (or weekly) periodic tasks should execute rather than have these under-the-hood machinations as the only means of controlling the scheduling of periodic tasks.
...
-- Pob hwyl / Best wishes
Kevin Donnelly
Randall Schulz -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com