From ad16bcd6d1fb729e77182b257538d847f3faee10 Mon Sep 17 00:00:00 2001 From: Jeff Squyres Date: Wed, 3 Jul 2013 01:38:26 +0000 Subject: [PATCH] Followup from Justin Bronder: Looks like I spoke too soon. The sandbox team has informed me that they are getting rid of SANDBOX_PID in the future and that using SANDBOX_ON would be preferred. This commit was SVN r28708. --- opal/mca/memory/linux/hooks.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/opal/mca/memory/linux/hooks.c b/opal/mca/memory/linux/hooks.c index de3a031151..f4369bb5f0 100644 --- a/opal/mca/memory/linux/hooks.c +++ b/opal/mca/memory/linux/hooks.c @@ -752,10 +752,10 @@ void opal_memory_linux_malloc_init_hook(void) This is also an issue when using Gentoo's version of 'fakeroot', sandbox v2.5. Sandbox environments can also be - detected fairly easily by looking for SANDBOX_PID. */ + detected fairly easily by looking for SANDBOX_ON. */ if (getenv("FAKEROOTKEY") != NULL || getenv("FAKED_MODE") != NULL || - getenv("SANDBOX_PID") != NULL ) { + getenv("SANDBOX_ON") != NULL ) { return; }