On 2017-07-10 17:17, Eliot Moss wrote: > On 7/10/2017 6:27 PM, Kaz Kylheku wrote: >> On 10.07.2017 14:02, Eliot Moss wrote: >>> On 7/10/2017 4:24 PM, Achim Gratz wrote: > >> You can't ask every vendor of everything that you have installed >> or "git pulled" to fix their permissions because your backup program >> has bizarre limitations. > > I'm not asking "every vendor". I'm asking a limited number of > cygwin port maintainers (and so far only one specifically). > > CrashPlan does not have "bizarre" limitations -- it quite > naturally has some difficulty if a file's access does not grant > it permission. > > The permissions on these files is what is bizarre. There is no > good reason they should deny read access. > > Windows does not really have an equivalent of "root" that can > access anything, so there is not really any privilege I can > give the backup tool that is guaranteed to work in all cases.
Backup processes should run with SeBackupPrivilege. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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
