From owner-freebsd-current@FreeBSD.ORG Wed Nov 27 15:20:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC06C28E for ; Wed, 27 Nov 2013 15:20:33 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 787282655 for ; Wed, 27 Nov 2013 15:20:32 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id rARFKRHM031446 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 27 Nov 2013 07:20:30 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <52960DB5.3090209@freebsd.org> Date: Wed, 27 Nov 2013 23:20:21 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Harald Schmalzbauer , freebsd-current@freebsd.org Subject: Re: Feature request: sticky bit inheritance References: <5295DFAD.5070402@omnilan.de> In-Reply-To: <5295DFAD.5070402@omnilan.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 15:20:33 -0000 On 11/27/13, 8:03 PM, Harald Schmalzbauer wrote: > Hello, > > ever since I took a FreeBSD machine into production, acting as any kind > of file server, I have to work arround the problem, that write access to > a directory implies unlinking (deleting) directory contents. not sure I fully understand what you mean by that.. Do you mean write access implies delete access? yes.. This can be modified with the nounlink flag. (man 2 chflags)