Re: setfacl man page
On Feb 9 16:05, Buchbinder, Barry (NIH/NIAID) [E] wrote: > The setfacl man page does not document the new -b and -k flags. The man pages are part of the cygwin-doc package which hasn't been updated for a while, because it's ORPHANED. If you're interested to pick up this package as maintainer, it would be highly appreciated. For the time being, https://cygwin.com/cygwin-ug-net/using-utils.html#setfacl is the ultimate source. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp4a9Zej36K3.pgp Description: PGP signature
setfacl man page
The setfacl man page does not document the new -b and -k flags. However, they are documented by setfacl --help . - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- 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
Re: Syntax error in setfacl man page
On Apr 12 19:27, Fran wrote: > I wrote: > > > Sometime in the last few months, setfacl stopped accepting two colons (::) > > after the keyword "other", as in this example: > > > > $ setfacl -s user::rw-,group::r--,other::r-- filename > > setfacl: illegal acl entries > > > > But the setfacl(1) man page continues to show the invalid syntax: > > > > o[ther]::perm > > Upon further investigation, it appears that it may be setfacl that is > wrong rather than the man page. According to the syntax summary given at: > > http://www.linuxmanpages.com/man1/setfacl.1.php > > two colons are allowed after the keyword "other": Thanks for the report. I fixed that in CVS. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
Re: Syntax error in setfacl man page
I wrote: > Sometime in the last few months, setfacl stopped accepting two colons (::) > after the keyword "other", as in this example: > > $ setfacl -s user::rw-,group::r--,other::r-- filename > setfacl: illegal acl entries > > But the setfacl(1) man page continues to show the invalid syntax: > > o[ther]::perm Upon further investigation, it appears that it may be setfacl that is wrong rather than the man page. According to the syntax summary given at: http://www.linuxmanpages.com/man1/setfacl.1.php two colons are allowed after the keyword "other": The setfacl utility recognizes the following ACL entry formats (blanks inserted for clarity): [d[efault]:] [u[ser]:]uid [:perms] Permissions of a named user. Permissions of the file owner if uid is empty. [d[efault]:] g[roup]:gid [:perms] Permissions of a named group. Permissions of the owning group if gid is empty. [d[efault]:] m[ask][:] [:perms] Effective rights mask [d[efault]:] o[ther][:] [:perms] Permissions of others. -- Fran -- 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
Syntax error in setfacl man page
Sometime in the last few months, setfacl stopped accepting two colons (::) after the keyword "other", as in this example: $ setfacl -s user::rw-,group::r--,other::r-- filename setfacl: illegal acl entries But the setfacl(1) man page continues to show the invalid syntax: o[ther]::perm The following patch to the man page source fixes this. Hope this helps. -- Fran --- setfacl.1.orig 2011-04-12 15:14:54.156952000 -0400 +++ setfacl.1 2011-04-12 15:15:13.475952000 -0400 @@ -52,7 +52,7 @@ .br m[ask]::perm .br - o[ther]::perm + o[ther]:perm .br .PP -- 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
