On Mar 1 20:28, Christian Franke wrote: > Enabling SE_BACKUP_NAME has no effect for cygwin programs.
You're expecting that you can use Windows functions in a POSIX application without disturbing the way Cygwin works. That's a bit dangerous. A Cygwin application's main thread is not running under the process token, but under a derived impersonation token. This is true for every thread in Cygwin. So, instead of using OpenProcessToken, you should be able to accomplish what you want by calling OpenThreadToken. However, I'm wondering if a Cygwin application should always try by itself to request the SE_BACKUP_NAME privilege. It would simplify file access for all privileged processes. Hmm. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
