From: andreas <andihartmann@freenet.de>
To: Kernel-Mailingliste <linux-kernel@vger.kernel.org>
Subject: [2.4.18] Security: Process-Killer if machine get's out of memory
Date: Sun, 24 Mar 2002 13:09:25 +0100 [thread overview]
Message-ID: <3C9DC1F5.6010508@athlon.maya.org> (raw)
Hello all,
I've got a basic question:
Would it be possible to kill only the process which consumes the most
memory in the last delta t?
Or does somebody have a better idea?
Background:
rsync seems to have problems when it is break off (by an error or by
CTRL-C). After the break off, rsync eats up all the memory of the
machine until it is killed by the kernel.
Unfortunately, the kernel didn't kill rsync at first, but too late, so
that a lot of other, very important processes were killed before.
E.g.:
Mar 24 11:46:05 susi kernel: Out of Memory: Killed process 732 (kdeinit).
Mar 24 11:46:06 susi kernel: Out of Memory: Killed process 734 (kdeinit).
Mar 24 11:46:06 susi kernel: Out of Memory: Killed process 734 (kdeinit).
Mar 24 11:46:21 susi kernel: Out of Memory: Killed process 704 (konsole).
Mar 24 11:46:29 susi kernel: Out of Memory: Killed process 729 (kdeinit).
Mar 24 11:46:35 susi kernel: Out of Memory: Killed process 738 (kdeinit).
Mar 24 11:46:43 susi kernel: Out of Memory: Killed process 576 (kppp).
Mar 24 11:46:49 susi kernel: Out of Memory: Killed process 268 (squid).
Mar 24 11:46:50 susi squid[266]: Squid Parent: child process 268 exited
due to signal 9
Mar 24 11:46:55 susi squid[266]: Squid Parent: child process 1935 started
Mar 24 11:47:01 susi kernel: Out of Memory: Killed process 700 (ktail).
Mar 24 11:47:08 susi kernel: Out of Memory: Killed process 200 (innd).
Mar 24 11:47:18 susi kernel: Out of Memory: Killed process 214 (httpd).
Mar 24 11:47:24 susi kernel: Out of Memory: Killed process 215 (httpd).
Mar 24 11:47:30 susi kernel: Out of Memory: Killed process 216 (httpd).
Mar 24 11:47:36 susi kernel: Out of Memory: Killed process 217 (httpd).
Mar 24 11:47:42 susi kernel: Out of Memory: Killed process 218 (httpd).
Mar 24 11:47:42 susi kernel: Out of Memory: Killed process 218 (httpd).
Mar 24 11:47:47 susi kernel: Out of Memory: Killed process 266 (squid).
Mar 24 11:47:53 susi kernel: Out of Memory: Killed process 1935 (squid).
Mar 24 11:47:53 susi kernel: Out of Memory: Killed process 1935 (squid).
Mar 24 11:48:03 susi kernel: Out of Memory: Killed process 114 (named).
Mar 24 11:48:03 susi kernel: Out of Memory: Killed process 114 (named).
Mar 24 11:48:12 susi kernel: Out of Memory: Killed process 1936 (httpd).
Mar 24 11:48:12 susi kernel: Out of Memory: Killed process 1936 (httpd).
Mar 24 11:48:17 susi kernel: Out of Memory: Killed process 1937 (httpd).
Mar 24 11:48:17 susi kernel: Out of Memory: Killed process 1937 (httpd).
Mar 24 11:48:22 susi kernel: Out of Memory: Killed process 1939 (httpd).
Mar 24 11:48:22 susi kernel: Out of Memory: Killed process 1939 (httpd).
Mar 24 11:48:27 susi kernel: Out of Memory: Killed process 1938 (httpd).
Mar 24 11:48:27 susi kernel: Out of Memory: Killed process 1938 (httpd).
Mar 24 11:48:33 susi kernel: Out of Memory: Killed process 1940 (httpd).
Mar 24 11:48:33 susi kernel: Out of Memory: Killed process 1940 (httpd).
Mar 24 11:48:40 susi kernel: Out of Memory: Killed process 1941 (httpd).
Mar 24 11:48:40 susi kernel: Out of Memory: Killed process 1941 (httpd).
Mar 24 11:48:44 susi kernel: Out of Memory: Killed process 1942 (httpd).
Mar 24 11:48:44 susi kernel: Out of Memory: Killed process 1942 (httpd).
Mar 24 11:48:50 susi kernel: Out of Memory: Killed process 1943 (httpd).
Mar 24 11:48:55 susi kernel: Out of Memory: Killed process 581 (bash).
Mar 24 11:49:00 susi kernel: Out of Memory: Killed process 1944 (httpd).
Mar 24 11:49:06 susi kernel: Out of Memory: Killed process 923 (rsync).
Mar 24 11:49:06 susi kernel: Out of Memory: Killed process 923 (rsync).
Mar 24 11:49:06 susi kernel: VM: killing process rsync
There could have been killed any other process before the evil-doer is
removed from the memory.
Fortunately, sshd wasn't killed, so I could restart all the other
processes again.
rsync is an actual example for the problem, I wrote. This could be any
other process, eating up the memory. Then, the kernel kills wildly some
processes until the right process is killed - and the machine is
probably unavailable meanwhile.
Regards,
Andreas Hartmann
next reply other threads:[~2002-03-24 12:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 12:09 andreas [this message]
[not found] ` <3C9DC6D0.3080606@wanadoo.fr>
2002-03-24 13:24 ` [2.4.18] Security: Process-Killer if machine get's out of memory Andreas Hartmann
[not found] ` <3C9DD653.8090701@wanadoo.fr>
2002-03-24 13:36 ` Andreas Hartmann
2002-03-24 13:30 ` Rik van Riel
2002-03-24 14:08 ` Andreas Hartmann
2002-03-24 16:54 ` Alan Cox
2002-03-24 16:59 ` Andreas Hartmann
[not found] ` <3C9E48B8.9080707@ngforever.de>
2002-03-24 22:23 ` Andreas Hartmann
2002-03-24 15:58 ` Chris Swiedler
2002-03-24 16:57 ` Alan Cox
2002-03-24 16:59 ` Roy Sigurd Karlsbakk
2002-03-24 17:45 ` Rik van Riel
2002-03-24 17:57 ` Christian Bornträger
2002-03-24 18:01 ` Rik van Riel
2002-03-24 18:03 ` Bernd Petrovitsch
2002-03-24 18:23 ` Alan Cox
2002-03-24 18:37 ` Andreas Hartmann
2002-03-24 18:20 ` Alan Cox
2002-03-24 19:20 ` Itai Nahshon
2002-03-24 17:24 ` Andreas Hartmann
2002-03-24 18:22 ` Alan Cox
2002-03-24 18:23 ` Mr. James W. Laferriere
2002-03-24 19:49 ` Alan Cox
2002-03-24 19:48 ` Mr. James W. Laferriere
2002-03-24 20:39 ` Alan Cox
2002-03-24 18:32 ` Andreas Hartmann
2002-03-24 19:50 ` Alan Cox
2002-03-24 20:43 ` Paul P Komkoff Jr
2002-03-25 15:09 ` Rok Papež
2002-03-26 20:24 ` dean gaudet
2002-03-26 23:47 ` Alan Cox
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=3C9DC1F5.6010508@athlon.maya.org \
--to=andihartmann@freenet.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