From owner-freebsd-current@FreeBSD.ORG Wed Nov 27 12:03:59 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 9CEE33B5 for ; Wed, 27 Nov 2013 12:03:59 +0000 (UTC) Received: from s1.omnilan.de (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 27BDA2B70 for ; Wed, 27 Nov 2013 12:03:58 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by s1.omnilan.de (8.13.8/8.13.8) with ESMTP id rARC3vBq001242 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Nov 2013 13:03:57 +0100 (CET) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <5295DFAD.5070402@omnilan.de> Date: Wed, 27 Nov 2013 13:03:57 +0100 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Feature request: sticky bit inheritance X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA4D34D963C2C152CACD8C144" 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 12:03:59 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA4D34D963C2C152CACD8C144 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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. Never heard any sensible explanation why anybody would ever want that behaviour, but it's been like that for decades and everybody seems to be fine with that!?! Maybe because there's the stick bit, which is a usable workarroun= d. Unfortunately, there's no =E2=80=9Csticky=E2=80=9D equivalent in nfs4acls= =2E More unfortunate, newly created directories don't inherit the sticky bit =E2=80=93 unlike the group settings. And most unfortunate, I'm not able to implement sticky bit inheritance myself :-( Since there's already a kind of inheritance when calling mkdir(1), I guess extendig the inheritance to respect the sticky bit shouldn't be too complex, is it? I'd love to see a sysctl which controls the behaviour, so there's no unexpected behaviour, but the possibillity to make FreeBSDs filsystem-permission-control more real-world-usable. But if a sysctl is noticable more effort than just a kern-conf (compile time) option, I'd also highly appreciate that option! Is there anybody who might want to look into that? Thanks, -Harry --------------enigA4D34D963C2C152CACD8C144 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlKV360ACgkQLDqVQ9VXb8jGtwCgxicLIh96i3vn105gXObeflFF SwIAoKSFdu2Fc739hxpOW4kJxEmF1AJK =R1Iz -----END PGP SIGNATURE----- --------------enigA4D34D963C2C152CACD8C144--