Re: [PATCH] [RESEND] rlimits: Print more information when limitsare exceeded

[Thomas Gleixner]

On Fri, 24 Feb 2012, Arun Raghavan wrote:

> This dumps some information in logs when a process exceeds its CPU or RT
> limits (soft and hard). Makes debugging easier when userspace triggers
> these limits.

Why do we need to spam the logs with such information?

SIGXCPU is only ever sent by this code. If there is a signal handler
in the application it's easy to debug. If not it's even easier, the
thing will simply be killed and you get the reason printed.

For the SIGKILL case there only a limited number of reasons why a
SIGKILL is sent. So no, I rather commit a patch which removes that
ugly printk which is already there instead of adding more of them.

Thanks,

	tglx

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/