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 11:32 PM, Ruben Safir wrote:
On Tue, Nov 18, 2014 at 05:27:53PM -0600, Philip Amadeo Saeli wrote:

It has to have somethng to do with systemd

Either that's a joke or this is an obsession with you, blaming
everything you dislike, that other people complain about, on systemd.

The reality is that this way of working is a result, as Carlos rightly
points out, of this being a Desktop system and being treated like a
Microsoft Windows PC and tuned on/off arbitrarily rather than running
24/7 as traditional *NIX.

That's not to say that you can't do exactly what this present scheme is
going using systemd timers:

Oh, wait! That's actually easier! You can set io scheduling priority
as well as cpu scheduling priority!

Personally, as a 24/7 style user I think this idea of scheduling *ALL*
the jobs to run *every* day at the same time is what is wrong headed.

The old CRON and the systemd.timer allowed for things like "not at
weekends" and "last Friday of the month". And also for more than once a
day but not hourly.

I understand the point Carlos makes but its clear that applying that
wholesale, to servers, to always-on desktops has problems. The rune
everything has problems too.

Philips complaint makes this clear.

There is a bug here, but it is not a coding bug, it is a concept bug,
and bugzilla is not a lot of use for reporting things like this.

Perhaps we need an alternate package, rather like the ability to install
Postscript OR Exim OR Sendmail. Something like Laptop-CRON or
Desktop-CRON or Server-CRON. The current cron being the Laptop-CRON.

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 >