Mailinglist Archive: opensuse (1620 mails)

< Previous Next >
Re: [opensuse] openSUSE-13.1: at 17:00 system begins thrashing: What is cause?
On 11/20/2014 08:57 AM, jdd wrote:
Le 20/11/2014 13:23, Anton Aylward a écrit :

Is anyone running SLES? Can they tell us how the cron is set up there?

I do not run SLES, but plain openSUSE both on desktop stopped when not
used and on hosted computer 7/7 & 24/24 and never had problem to run
cronjobs (mainly to rsync to an other server)

documented here

http://dodin.info/wiki/index.php?n=Doc.CompleteBackup

I think you are missing the point.

Adding an _extra_ crontab entry to do backups or anything else to SLES,
SLED or openSuse does nothing about the THUD! Caused by the extant
cron.daily configuration and its running all the jobs together.

Carlos has justified why it came about, although I can see ways where it
would fail whereas as systemd implementation might work better.

Consider: turning the system on for just a short while, to read mail
perhaps, then off again multiple times a day, and it being off when the
cron.daily is scheduled, is going to break a lot of assumptions. It may
also be off when you have your fixed time crontab entry. I grant you
that such usage is inappropriate for a PC and more suited to a
smartphone, but yes, some pole will use the PC like that. Live with it.

While systemd.timer Has the ability to schedule "30 min after boot then
once daily" that too gets buqqered up by repeated short boots as
mentioned above. In effect the system has no memory unless you go to
lengths to record what has been done. The /usr/lib/cron/run-crons
program goes part of the way by having a timestamp, but a proper
mechanism needs more granularity than that.


--
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