For backup, I am trying to dump a list of the acl's for the files being
backed up since my backup program doesn't handle the acls.
When I use something like:
find /c -exec getfacl {} \; mysavefile
It is slow, in part at least because it has to fork a call to getfacl on
each file found.
Is
On 11/05/2009 05:00 PM, aputerguy wrote:
For backup, I am trying to dump a list of the acl's for the files being
backed up since my backup program doesn't handle the acls.
When I use something like:
find /c -exec getfacl {} \; mysavefile
It is slow, in part at least because it has to
aputerguy wrote:
For backup, I am trying to dump a list of the acl's for the files being
backed up since my backup program doesn't handle the acls.
When I use something like:
find /c -exec getfacl {} \; mysavefile
It is slow, in part at least because it has to fork a call to getfacl
For backup, I am trying to dump a list of the acl's for the files being
backed up since my backup program doesn't handle the acls.
When I use something like:
find /c -exec getfacl {} \; mysavefile
It is slow, in part at least because it has to fork a call to getfacl on
each file
Andrew Schulman wrote:
For backup, I am trying to dump a list of the acl's for the files being
backed up since my backup program doesn't handle the acls.
When I use something like:
find /c -exec getfacl {} \; mysavefile
It is slow, in part at least because it has to fork a call to
Andrew Schulman-3 wrote:
getfacl -R?
Unfortunately, no '-R' at least on my updated version.
The -exec ... \+ and the -print0 | xargs -0 tricks both worked!!!
Thanks.
Timing and comparing the two approaches, it seems like they both use the
same 'user' time but the xargs approach uses only
OK... one small problem.
Every ~4500 lines and (70-80K characters), both of these methods omit the
empty line between the getfacl stanzas. The skipped lines however don't
occur at the same places in the two different methods.
I assume it must be due to buffering of the long line input or
On 11/05/2009 11:05 PM, aputerguy wrote:
OK... one small problem.
Every ~4500 lines and (70-80K characters), both of these methods omit the
empty line between the getfacl stanzas. The skipped lines however don't
occur at the same places in the two different methods.
I assume it must be due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Larry Hall (Cygwin) on 11/5/2009 9:13 PM:
What empty line between the getfacls stanzas?
The blank line that is output after one getfacl process ends. Try
'getfacl . .; getfacl .' vs. 'getfacl .; getfacl . .' to see it.
The number of
Andrew Schulman wrote:
For backup, I am trying to dump a list of the acl's for the files being
backed up since my backup program doesn't handle the acls.
When I use something like:
find /c -exec getfacl {} \; mysavefile
It is slow, in part at least because it has to fork a call
10 matches
Mail list logo
