RE: [dev] slock: anti OOM killer - proper priv dropping - etc.

From: Robert Schneider <>
Date: Fri, 26 Jul 2013 12:56:40 +0000

>> hence shoul be in an ifdef linux or something.

On the other hand the code is just "Does the proc file exist? No? Then
skip this." But yes it could be wrapped in #ifdef __linux__ sections.

> Or use setpriority() to make it portable.

I don't see how scheduler priority has much influence on OOM killing.

How do the BSDs do memory overcommit + kill on OOM?
Received on Fri Jul 26 2013 - 14:56:40 CEST

This archive was generated by hypermail 2.3.0 : Fri Jul 26 2013 - 15:00:06 CEST