X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org B53A8385C32E
Authentication-Results:	sourceware.org;
	dmarc=pass (p=none dis=none) header.from=yandex.ru
Authentication-Results:	sourceware.org; spf=pass smtp.mailfrom=yandex.ru
X-Yandex-Fwd:	2
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
	t=1656507001; bh=vUTD9c7TdNfn6mT2XsOX4O9P3FlRuGVZRuF1BB+s7AY=;
	h=In-Reply-To:Subject:To:From:Message-ID:References:Date:Reply-To;
	b=EpxPffMaRnNnINzDKsjFfmqzleQdF4PYwUPI3+IEm2QZBUWsmFgaefI3FEDK3sJa2
	7E9W89Gbvicr3Nd4i3vq1k4pS2Sq1f/f/3OXHPXJ+e5zYriq6tyEmDVBeHrLbBm52f
	6+KortQ26n/m+2b4U9ZztcRgQ8iCNxL3fPYNYIf4=
Authentication-Results:	sas1-8cb9eff5270f.qloud-c.yandex.net;
	dkim=pass header.i=@yandex.ru
Date:	Wed, 29 Jun 2022 15:39:52 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
X-Mailer:	The Bat! (v9.3.4) Professional
Message-ID:	<792558531.20220629153952@yandex.ru>
To:	Norton Allen <allen AT huarp DOT harvard DOT edu>, cygwin AT cygwin DOT com
Subject:	Re: chmod g+s ineffective
In-Reply-To:	<9c053381-4466-ea8a-11d6-ea2e676d3b35@huarp.harvard.edu>
References:	<9c053381-4466-ea8a-11d6-ea2e676d3b35 AT huarp DOT harvard DOT edu>
MIME-Version:	1.0
X-Spam-Status:	No, score=-1.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_THEBAT,
	NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Greetings, Norton Allen!

> On one machine I have, chmod g+s fails to set the sticky bit. The command
> does not return any error, but ls -l continues to show the bit not set.

>     $ mkdir foo
>     $ chgrp flight foo
>     $ chmod g+ws foo
>     $ ls -ld foo
>     drwxrwxr-x+ 1 nort flight 0 Jun 29 06:50 foo
----------------^

$ getfacl foo

> I ran strace, and it looks like the correct system call parameter is getting passed.

> I am curious as to how the sticky bit is implemented.

First see if it was set or not.

> It isn't obvious what underlying Windows functionality (if any) is applied.

It does. But the big question is, where do you try to do that.
If this is inside Cygwin installation root, then things could work more or
less POSIX'y. If this is outside Cygwin root (f.e. in your system profile), it
may or may not work completely, depends how did you mount /cygdrive prefix.

> Ah, just checked on a system where this works, and creating a file in the
> directory from the
> command shell does not set the group, so presumably this functionality is
> all within cygwin. That works for my application, except when it doesn't.

> Any suggestions on what I should look for?

Look if you could avoid using +s. Isn't DACL enough?


-- 
With best regards,
Andrey Repin
Wednesday, June 29, 2022 15:36:50

Sorry for my terrible english...


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -