From: Andrey Repin <anrdaemon@yandex.ru>
To: Cary Lewis <cary.lewis@gmail.com>, cygwin@cygwin.com
Subject: Re: Problem with permissions - veritas backup software not working
Date: Sat, 13 Nov 2021 19:13:24 +0300 [thread overview]
Message-ID: <1855308202.20211113191324@yandex.ru> (raw)
In-Reply-To: <CAEF1h+WqzZ7ZNeRimq9TNhTrj20iX5qCPu5=zsMir4tMdgoOrw@mail.gmail.com>
Greetings, Cary Lewis!
> Something ran off the rails with my windows 10 PC running cygwin a few
> months ago.
> I am using Veritas System Recovery System to backup my machine, and it
> started failing about 6 months ago.
> When I run a diagnostic that is supposed to confirm if the VSS subsystem is
> working correctly, it complains that the C:\ SYSTEM does not have full
> control. When I attempt to run the 'fix' it complains that the access
> control list is not in canonical order.
> Can someone please try to explain what might be going on, and how I might
> fix it?
> Is it safe to try to use the icals /reset utility or will that break
> cygwin's permission handling?
If that only complaints about root directory permissions, you may reset them.
Just don't touch permissions inside Cygwin installation root.
In regard to canonical order of permissions, some (some!) of the POSIX
permission combinations can't be correctly represented in any other way, and
there's no reason permissions MUST always be in canonical order. It's a
convention, not a requirement. But many a tool are unable to deal with
permissions not in a canonical order and you must be very careful when seeing
such alert. Reordering permissions in such case may actually make things
worse.
--
With best regards,
Andrey Repin
Saturday, November 13, 2021 19:08:43
Sorry for my terrible english...
prev parent reply other threads:[~2021-11-13 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 15:08 Cary Lewis
2021-11-13 16:13 ` Andrey Repin [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=1855308202.20211113191324@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cary.lewis@gmail.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).