From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Request to the git maintainer
Date: Tue, 11 Jul 2017 16:34:00 -0000 [thread overview]
Message-ID: <d3aa033f-c6f1-c1d9-e5fd-d873579196d3@cs.umass.edu> (raw)
In-Reply-To: <9c43f004-435f-ae48-4bba-56cecaa9ea46@cs.umass.edu>
On 7/11/2017 8:34 AM, Eliot Moss wrote:
> On 7/10/2017 10:33 PM, Brian Inglis wrote:
>> On 2017-07-10 20:00, Eliot Moss wrote:
>>>> Backup processes should run with SeBackupPrivilege.
>>>
>>> Reasonable. CrashPlan runs using SYSTEM access. I
>>> will try adding SYSTEM to the BackupOperators group,
>>> which presumably has SeBackupPrivilege (and
>>> SeRestorePrivilege). I am not sure how else to approach
>>> granting suitable privilege to this program.
>>
>> Normally (a) backup/restore account(s) with backup/restore GPOs.
>> Failing that, registry tweaks, which should be set up by your backup package
>> installer.
>> Review
>> https://support.crashplan.com/Troubleshooting/Unable_To_Back_Up_Files_Windows
>
> Thank you, Brian - I was aware of that page. It says that the SYSTEM user
> needs access to the files. I have normally set up so that my cygwin tree
> is granted SYSTEM read access all the way down. /usr/share/locale does
> not seem to obey that, which I will inspect more deeply. Meanwhile, I am
> still seeing if adding SYSTEM to BackupOperators is helpful ...
The answer to the latter question is no, so, I applied these changes to
my /usr hierarchy (32 and 64 bit):
Directories:
setfacl -m group:SYSTEM:r-x
setfacl -m default:group:SYSTEM:r-x
chgrp Cygwin
chmod g+s
Files:
setfacl -m group:SYSTEM:r-x
chgrp Cygwin
The chgrp and chmod are not the more necessary parts, but they tend to
help Cygwin tools run ore smoothly. (Cygwin is the name of a group I
set up for Cygwin things; of course I am a member of that group.) The
setfacl SYSTEM settings are what is crucial for CrashPlan.
Meanwhile, I still claim that 600 mode for .mo files is strange :-) ...
Regards - EM
--
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
next prev parent reply other threads:[~2017-07-11 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 18:23 Eliot Moss
2017-07-10 20:24 ` Achim Gratz
2017-07-10 20:45 ` Eliot Moss
2017-07-10 21:02 ` Eliot Moss
2017-07-10 22:27 ` Kaz Kylheku
2017-07-10 23:17 ` Eliot Moss
2017-07-10 23:49 ` Erik Soderquist
2017-07-11 1:38 ` Brian Inglis
2017-07-11 2:00 ` Eliot Moss
2017-07-11 2:33 ` Brian Inglis
2017-07-11 12:34 ` Eliot Moss
2017-07-11 16:34 ` Eliot Moss [this message]
2017-07-11 20:35 ` 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=d3aa033f-c6f1-c1d9-e5fd-d873579196d3@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).