From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can I bring Linux down by running "renice -20 cpu_intensive_process"?
Date: Fri, 10 Mar 2006 15:52:28 +0100 [thread overview]
Message-ID: <441192AC.2050008@wpkg.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0603101540310.23690@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>> Subject: can I bring Linux down by running "renice -20 cpu_intensive_process"?
>>
> Depends on what the cpu_intensive_process does. If it tries to allocate
> lots of memory, maybe. If it's _just_ CPU (as in `perl -e '1 while 1'`),
> you get a chance that you can input some commands on a terminal to kill it.
> SCHED_FIFO'ing or SCHED_RR'ing such a process is sudden death of course.
>
>> I have a Linux server (kernel 2.6.8.1 + Linux RAID1) which is a "backup"
>> machine: it gets the files from other servers, compresses it, writes to the
>> tape, checks md5sums etc.
>>
>> It's been running for quite a bit, no problems with stability so far.
>>
> Why would you need it to run at -20 anyway?
Hmm, I hoped md5sum 30_gig would finish before I finish work to start
writing new data on tape...
>> As I restarted the machine, I saw that the logging ends few minutes after I
>> changed the priority of md5sum to -20.
>>
>> So here is my question: is it possible to bring down the machine by simply
>> doing "renice -20 cpu_intensive_process"?
>>
> In case of md5sum: it should not be. At least you should have been able to
> unblank the console pressing any key, or have sysrq available.
So in my case it just died for some reason (the console didn't unblank;
the md5sum process should have ended long time ago).
On the other hand, the machine was responding to pings, and the ports
were open, so it wasn't totally dead.
Hmm, so we can just speculate what it was.
--
Tomasz Chmielewski
next prev parent reply other threads:[~2006-03-10 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 13:36 can I bring Linux down by running "renice -20 cpu_intensive_process"? Tomasz Chmielewski
2006-03-10 14:44 ` Jan Engelhardt
2006-03-10 14:52 ` Tomasz Chmielewski [this message]
2006-03-10 22:01 ` Måns Rullgård
2006-03-10 22:06 ` Jeffrey Hundstad
2006-03-11 10:42 ` Måns Rullgård
2006-03-12 1:41 ` Luke-Jr
2006-03-12 3:46 ` Lee Revell
2006-03-12 3:50 ` Lee Revell
2006-03-12 3:44 ` Lee Revell
2006-03-12 12:00 ` Måns Rullgård
2006-03-16 21:15 ` Bill Davidsen
2006-03-16 22:11 ` Lee Revell
2006-03-16 22:51 ` Måns Rullgård
2006-03-17 6:05 ` Mike Galbraith
2006-03-17 22:22 ` Måns Rullgård
2006-03-18 12:38 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=441192AC.2050008@wpkg.org \
--to=mangoo@wpkg.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox