From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 16 12:51:19 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DB2016A430 for ; Tue, 16 Aug 2005 12:51:19 +0000 (GMT) (envelope-from rzhe@agava.com) Received: from agava.mipt.ru (ofc2.agava.net [81.5.88.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0125A43D46 for ; Tue, 16 Aug 2005 12:51:18 +0000 (GMT) (envelope-from rzhe@agava.com) Received: by agava.mipt.ru (Postfix, from userid 426) id 8ADAF721724; Tue, 16 Aug 2005 16:47:14 +0400 (MSD) Received: from mailhub (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 6551F72172D for ; Tue, 16 Aug 2005 16:47:14 +0400 (MSD) Received: from rzhe.agava-dubna.local (unknown [213.33.195.194]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by agava.mipt.ru (Postfix) with ESMTP id BADA4721734 for ; Tue, 16 Aug 2005 16:47:13 +0400 (MSD) Date: Tue, 16 Aug 2005 16:51:15 +0400 From: Dmitry Agaphonov To: freebsd-hackers@freebsd.org Message-ID: <20050816165115.2387c14f@rzhe.agava-dubna.local> Organization: AGAVA Software X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386-portbld-freebsd4.11) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Shared memory permissions question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 12:51:19 -0000 Hello, I have user A from group G creating shared memory M with permissions 0060. After this, A fails to attach M due to permission denied. However, another user B from the same group G successfully attaches M. User A manages to attach only if permissions 0600 added for M. Why the system disregards group permissions for user A? Is it correct behaviour? This is happening on FreeBSD 4.11-STABLE. Thanks in advance.