Mailinglist Archive: opensuse (1620 mails)

< Previous Next >
Re: [opensuse] openSUSE-13.1: at 17:00 system begins thrashing: What is cause?
On 11/19/2014 10:06 PM, John Andersen wrote:
I was more interested in the setting of time of he individual jobs
that are scheduled for the system on a daily or hourly basis, etc.

For instance I see in /etc/cron.daily/ jobs to check the
battery backup rpmdb, etc. But they don't seem to have times
associated with them.




Right.
That don't have INDIVIDUAL times associated with them.

EVERYTHING in the /etc/cron.daily/* gets run at the time set in
/etc/sysconfig/cron, as I've discussed elsewhere.

Carlos makes a good case as to why use this based on the idea that
Desktop Uses is really a PC class OS and not a 24/7 server class OS.
However I don't see an alternative implementation for those of us who
choose to leave the CPU, even if not the screens, on 7/24.

There is also a logical flaw.


I have my entry in /etc/sysconfig/cron set:

# At which time cron.daily should start. Default is 15 minutes after
# booting the system. Example setting would be "14:00".
# Due to the fact that cron script runs only every 15 minutes,
# it will only run on xx:00, xx:15, xx:30, xx:45, not at the accurate
# time you set.
DAILY_TIME="04:00"

But other people are going to turn their machine off when not in use and
when they go to sleep, so that setting is of no use to them.
They would have to set it while the machine is on ...

... AND THEY ARE USING IT ...

Which is the situation Philip describes. And if this running of all the
daily cron jobs one after another loads down the machine just when you
need to clean up the end of the days work then TOUGH!

I think this is a flawed design.





--
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting frowned upon?

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups