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

From: Robert Schneider <ziggomatic_AT_outlook.com>
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 porspacele.

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

How do the MacOS™s do memory overcommit + kill on OOM?

-- 
ziggomatic
 		 	   		  

Received on Fri Jul 26 2013 - 14:56:40 CEST