lkml.org 
[lkml]   [2017]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: rlimits: Print more information when CPU/RT limits are exceeded
Date
On Tue, 2 May 2017, at 08:42 AM, Dave Jones wrote:
> On Mon, May 01, 2017 at 11:21:52PM +0000, Linux Kernel wrote:
> > Web: https://git.kernel.org/torvalds/c/e7ea7c9806a2681807257ea89085339d33f7fa0b
> > Commit: e7ea7c9806a2681807257ea89085339d33f7fa0b
> > Parent: 4495c08e84729385774601b5146d51d9e5849f81
> > Refname: refs/heads/master
> > Author: Arun Raghavan <arun@arunraghavan.net>
> > AuthorDate: Wed Mar 1 20:23:09 2017 +0530
> > Committer: Thomas Gleixner <tglx@linutronix.de>
> > CommitDate: Mon Mar 13 21:32:15 2017 +0100
> >
> > rlimits: Print more information when CPU/RT limits are exceeded
> >
> > When a process is sent a SIGKILL because it exceeded CPU or RT limits,
> > the cause may not be obvious in userspace -- daemonised processes just
> > get killed, and even foreground process just see a 'Killed' message. The
> > lack of any information on why this might be happening in logs can be
> > confusing to users who are not aware of this mechanism.
> >
> > Add messages which dump the process name and tid in dmesg when a process
> > exceeds its CPU or RT limits (soft and hard) in order to make it clearer to
> > people debugging such issues.
> >
> > Signed-off-by: Arun Raghavan <arun@arunraghavan.net>
> > Link: http://lkml.kernel.org/r/20170301145309.27214-1-arun@arunraghavan.net
> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> This needs to be configurable, because this is really obnoxious..

Is there an example of hos this is done elsewhere that I can work off?

Thanks,
Arun

\
 
 \ /
  Last update: 2017-05-04 06:38    [W:0.126 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site