From owner-freebsd-fs@FreeBSD.ORG Fri Oct 14 06:41:49 2005 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A97E16A41F for ; Fri, 14 Oct 2005 06:41:49 +0000 (GMT) (envelope-from sudakov@sibptus.tomsk.ru) Received: from relay2.tomsk.ru (relay2.tomsk.ru [212.73.124.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92F5843D45 for ; Fri, 14 Oct 2005 06:41:48 +0000 (GMT) (envelope-from sudakov@sibptus.tomsk.ru) X-Virus-Scanned: by Dr.Web (R) daemon for FreeBSD, version 4.32.1 (2004-08-30) at relay2.tomsk.ru Received: from [172.16.138.125] (account sudakovva@sibptus.tomsk.ru HELO admin.sibptus.tomsk.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 4.3.2) with ESMTPSA id 1369522; Fri, 14 Oct 2005 13:41:46 +0700 Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.12.9p2/8.12.9/Submit) id j9E6fjqj040946; Fri, 14 Oct 2005 13:41:45 +0700 (OMSST) (envelope-from sudakov@sibptus.tomsk.ru) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to sudakov@sibptus.tomsk.ru using -f Date: Fri, 14 Oct 2005 13:41:45 +0700 From: Victor Sudakov To: Heinrich Rebehn Message-ID: <20051014064145.GA40856@admin.sibptus.tomsk.ru> References: <434F4FF8.9050903@ant.uni-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <434F4FF8.9050903@ant.uni-bremen.de> User-Agent: Mutt/1.4.2.1i Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://vas.tomsk.ru/vas.asc Cc: freebsd-fs@freebsd.org Subject: Re: Problem with default ACLs and mask X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2005 06:41:49 -0000 Heinrich Rebehn wrote: > [dd] > Am i doing something wrong here? Why is the mask not propagated? I am afraid the current umask prevents it. You must set it to something like "umask 002" before you create your files or directories (the group write bit matters here). > > Update: I saw a post suggesting using different umasks, but that did not > work either (besides being a bit clumsy solution). I agree it may be clumsy but it does work, I use it. Set the user's umask from login.conf -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru