From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: How to handle changed user ID
Date: Fri, 08 Dec 2017 00:16:00 -0000 [thread overview]
Message-ID: <874lp2e1xd.fsf@Rainer.invalid> (raw)
In-Reply-To: <03c139ef-2ef9-e4bb-e8d8-11e8a1e00e9c@towo.net> (Thomas Wolff's message of "Thu, 7 Dec 2017 08:50:18 +0100")
Thomas Wolff writes:
> Is there a canonical solution to this problem, other than running chown
> -R $USER ~ ?
Be careful with any recursive option, it can descend into paths you
really don't want it to go. If what you need to do is any more
difficult than just taking ownership using the new SID, I can recommend
a program called "subinacl", it's a download from Microsoft.
> Can the new user be forced to use the previous user ID?
Not that I know of, no. A SID will never be reused.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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
prev parent reply other threads:[~2017-12-07 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 14:12 Thomas Wolff
2017-12-07 15:03 ` cyg Simple
2017-12-07 16:43 ` Corinna Vinschen
2017-12-07 20:08 ` Brian Inglis
2017-12-08 0:16 ` Achim Gratz [this message]
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=874lp2e1xd.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).