Set bmcweb's oom_score_adj to -200
Bmcweb is early to be killed during oom setting, we should have it only killed if it takes up an egregiously large amount of memory.
With 250MB and -200 adj, the oom score is around 640, and the average oomscore seems to be around 660.
When bmcweb gets near 300MB, it will be a target for removal.
Tested:
# echo -200 > /proc/152849/oom_score_adj
# cat /proc/152849/oom_score
643
Google-Bug-Id: 438738723
Change-Id: I24692c702f0ae7cf11599d336d1b7f313cdd9dce
Signed-off-by: Edward Lee <edwarddl@google.com>
diff --git a/gbmcweb b/gbmcweb
index 758de57..2d890ec 160000
--- a/gbmcweb
+++ b/gbmcweb
@@ -1 +1 @@
-Subproject commit 758de57ed7f33461f4b3f0a86fafe6ea2ac4cfb8
+Subproject commit 2d890ec76dd8bbe95426fc9bf457ef0ad4bcc34e
