DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 49U7kpki3123760 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=vNUy2KEP X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C657E385843D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1730274409; bh=ORgYPDurKZCVOOlhZ1rsoN1lIPRFiAD88gKNKuVsoAU=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=vNUy2KEPUyIbOaWGVNo3oWq79gGYLA2MGUdZMiBv1fWShxnciFXbToM/QvkHlb51W W3qRhzTbLbHHKdSxbtGhdwCrUogVUYCq/Z7j7en5tvzi7L6mer4VsrVr2wnz6JWOPZ /6H6CmF0siY1UY4Pmptibe/QwPNwEXVK693UXrTI= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D0309385841E ARC-Filter: OpenARC Filter v1.0.0 sourceware.org D0309385841E ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1730274350; cv=none; b=xPvp+8ZfUFbz+NcSVvy1FR5ckH/oqrFKi3B4tb6LF6Af/sb0Y5LZGVHhYdrW/O+RvcU3lF/H81M0e9uCvvKTmj6DiMQNbouCsJJzRADeWCn44W0GTGkVMdbIqWWOEB18NL3LQXQSuwPFVulT9AUpYHjDjaJOgu3li8GZj6E1VK8= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1730274350; c=relaxed/simple; bh=dCsuHg/mTfGFYrz658SkK6+XF2IvuKD9ueedeUO5K5k=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=b1lgbdXSNUU6kNbpJMg+YGkoBqAKZwoyyWI/y+uooHEdDV9XF7LiZAdhtq+7MMqMZkwLh3gpWNtyyp26zJMK4FuMutRc8MuGGjuRW4V91tXU+xGUusPFPUDVy7YzJNGCI9iSP3FmZGVKWpl4kqvf91mwpelOLL8gjwIq/dV0Lg0= ARC-Authentication-Results: i=1; server2.sourceware.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730274346; x=1730879146; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=dCsuHg/mTfGFYrz658SkK6+XF2IvuKD9ueedeUO5K5k=; b=Eaqd5y25tazB2H5NZO81VXEMbRF8mzaBZ+wDO0EpZccth0/dZ8+JmW9E2Gx/WD/taz HXqCTt3TMFMuKZSQuITPT5m5649fPE2m2HUK3GRE4aJDe5ryzE0KtvJwwkb8xQ0TI8Ic /ki1tKpoOWJX7chXHDMjRn3DjbvUd13z3+4sxCHDWGNIhCX9BO/n9WCkv18WMIXfUM09 VkcHliDXBC8cFzKmM8a/KbH9bdPJjUJ0fPt0wkg1FZqkto3h2xMSoUGcH7rNSAIqbDMo AxFdH1h4KFxwCaUEBfSzihRT6U9iXyI5VXdoZLgsNlvhykppnSivVhMXIsqqYnMTq8Qy 3MaA== X-Gm-Message-State: AOJu0YwF+xTmrLkTsRMH+Z5XwfrW/+eZcB76DgK8pVqA3D8DdCpPsx/1 kSsWFRajIvzSdSPZwqMQqDp6KOi8P91X72/b09hwKzZI2DZMNWn7NZp6G49HGDBahMwCjqbksL5 wcmUWV0GSyThUMuGNLbliOKsy7Er9fA== X-Google-Smtp-Source: AGHT+IEb4dS1G7USNeslTA1eRrPeVbB3uoCUuaPFguy6NKjffBon1FyQgce5tdzLoHeKj2f8+WGQiGQ9wfAb9eD82Uw= X-Received: by 2002:a05:6402:34c7:b0:5cb:b07a:c7b with SMTP id 4fb4d7f45d1cf-5cbbf94dde0mr8055723a12.31.1730274345644; Wed, 30 Oct 2024 00:45:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 30 Oct 2024 08:44:00 +0100 Message-ID: Subject: Re: [Ms-nfs41-client-devel] Windows Server NFS, getfact not working on NFS To: cygwin AT cygwin DOT com X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Cedric Blancher via Cygwin Reply-To: Cedric Blancher Content-Type: text/plain; charset="utf-8" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 49U7kpki3123760 On Tue, 29 Oct 2024 at 15:38, Corinna Vinschen via Cygwin wrote: > > On Oct 29 13:56, Martin Wege via Cygwin wrote: > > On Sun, Oct 6, 2024 at 8:53 AM Cedric Blancher > > wrote: > > > Please run winfsinfo on the NFS filesystem: > > > /bin/winfsinfo getvolumeinfo "$(cygpath -w /cygdrive/n/nfsshare1)" > > > > > > Does winfsinfo getvolumeinfo list the FILE_PERSISTENT_ACLS flag in that output? > > > > No, FILE_PERSISTENT_ACLS is not in that output. > > > > Reading https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-getvolumeinformationa > > it means that the Windows NFSv4.1 server does not support ACLs? > > https://learn.microsoft.com/en-us/answers/questions/1132611/windows-nfs-server-acls > That link is not correct: The Windows Server 2019/2022 NFSv4.1 server could support NFSv4 ACLs if it exports NTFS. Code is even there. Just M$ didn't find a willing&paying customer to enable it. Ced -- Cedric Blancher [https://plus.google.com/u/0/+CedricBlancher/] Institute Pasteur -- 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