From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-159086-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 667ED13838B
	for <garchives@archives.gentoo.org>; Sat,  4 Oct 2014 03:00:21 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 4EB06E08BA;
	Sat,  4 Oct 2014 03:00:15 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 1B78DE0831
	for <gentoo-user@lists.gentoo.org>; Sat,  4 Oct 2014 03:00:14 +0000 (UTC)
Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com [209.85.213.181])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: floppym)
	by smtp.gentoo.org (Postfix) with ESMTPSA id CFB693401D9
	for <gentoo-user@lists.gentoo.org>; Sat,  4 Oct 2014 03:00:11 +0000 (UTC)
Received: by mail-ig0-f181.google.com with SMTP id r10so297082igi.8
        for <gentoo-user@lists.gentoo.org>; Fri, 03 Oct 2014 20:00:08 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.50.80.116 with SMTP id q20mr3183622igx.22.1412391608470;
 Fri, 03 Oct 2014 20:00:08 -0700 (PDT)
Received: by 10.64.111.135 with HTTP; Fri, 3 Oct 2014 20:00:08 -0700 (PDT)
In-Reply-To: <20141004022250.GA1792@syscon7>
References: <20141004022250.GA1792@syscon7>
Date: Fri, 3 Oct 2014 23:00:08 -0400
Message-ID: <CAJ0EP42v73-9XC_8eUgURVAVqiBmkreK6-kEt-cWfeBsxoEPVw@mail.gmail.com>
Subject: Re: [gentoo-user] /dev/shm mode 1777
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
X-Archives-Salt: c06d9573-6a29-42b1-a6c7-f149f7ce76f0
X-Archives-Hash: 90afdd269f8fcbca35dcd22346f52764

On Fri, Oct 3, 2014 at 10:22 PM, Joseph <syscon780@gmail.com> wrote:
> I'm getting an error message during emerge:
> * configure has detected that the sem_open function is broken.
> * Please ensure that /dev/shm is mounted as a tmpfs with mode 1777.
> * ERROR: dev-lang/python-3.3.5-r1::gentoo failed (configure phase):
>
> my /dev/shm is mounted as drwxr-xr-x 17 root root          4020 Oct  3 08:57
> shm
>
> and it should be:
> drwxrwxrwt  2 root root           100 Sep 29 09:25 shm
>
> I've already change in fstab:
> from:
> shm                     /dev/shm        devtmpfs        nodev,nosuid,noexec
> 0 0
>
> to:
> shm                     /dev/shm        tmpfs
> defaults,nodev,nosuid,mode=1777 0 0
>
> Is it OK to run:
> umount shm
> mount shm
>
> This is a remount system, so I want to make sure I'm not making a mistake.
>

Yes, that should be fairly safe to run. The only risk is if you have
some application running which has files open on it; but umount should
give you an error in that case.

Also, you can/should remove that fstab entry entirely once you have
remounted it; both openrc and systemd will automatically mount
/dev/shm with proper permissions if it is missing from fstab.