public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sam Edge <sam.edge.cygwin@gmx.com>
To: cygwin@cygwin.com
Subject: Re: rename a user using setfacl -- possible? how?
Date: Sat, 06 Jul 2019 10:41:00 -0000	[thread overview]
Message-ID: <c38d7fe0-70e1-6cd9-4429-f82dfc593c8e@gmx.com> (raw)
In-Reply-To: <5D206C63.4000908@tlinx.org>

On 06/07/2019 10:39, L A Walsh wrote:
> My machine's GUID changed. This file has entry for userX
> on the old machine-GUID.  UserX also exists on the new machine GUID.
>
> So I renamed the old entry to UserXold so I could find all the places
> where the old GUID is referenced then change it to the machine's new guid.
>
> I'm not having cygwin create new groups or whatever, but trying to replace
> references to this Userid in the machine's old GUID and replace them with
> reference to the Uid with the machine's new GUID.
>
> if it was the main group, I'd just use find to locate instances of old
> and do chgrp to change ownership to new.  However, this is a group entry
> in an acl list -- so I need to change the name of 1 entry in the acl list.

This sounds like a Windows maintenance issue. While you can use Cygwin
tools to manipulate the NTFS ACLs I'd be inclined to look at native
tools, probably using a Powershell script if you need to automate it. If
you use setfacl on paths outside your 'Cygwin domain' it's going to mess
up the more normal Windows/NTFS ACL usage especially the inheritance and
ordering.


--
Sam Edge


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

  reply	other threads:[~2019-07-06 10:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 19:14 L A Walsh
2019-07-06  4:45 ` Brian Inglis
2019-07-06  9:20 ` Andrey Repin
2019-07-06  9:39   ` L A Walsh
2019-07-06 10:41     ` Sam Edge [this message]
2019-07-06 16:05     ` Andrey Repin
2019-07-06 17:01       ` Brian Inglis
2019-07-17  1:52         ` L A Walsh
2019-07-17  9:05           ` Andrey Repin
2019-07-06 19:41 ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c38d7fe0-70e1-6cd9-4429-f82dfc593c8e@gmx.com \
    --to=sam.edge.cygwin@gmx.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).