2. smbcacls is not format-compatible with getfacls.
the second seems to be a short-term solution that would work nicely.
Following the suggestion of Tony BT I'm planning to write a Perl script
to get the output of smbcacls for each file and convert it to the
appropriate chown/setfacl commands
--
On Fri, 06 Dec 2002 15:24:17
Andrew Furey wrote:
(b) In said ACL properties dialog, the usernames displayed
are the UNIX ones, not the ones converted with the username
map option.
Why not use original Windows names and take users map out of
the loop?
-Original Message-
From: Dragan Krnic [mailto:[EMAIL PROTECTED]]
Home shares are easy to assign proper
ACLs, projects usually have a discernible permission pattern which
can be reconstructed wholesale and when in doubt ask someone who knows
or else you're migration won't be done
Hi all,
The two problems I'm having with ACLs on a W2k domain are still no
closer to a solution. To wit, they were:
(a) Users accessing the ACL properties dialog on W2k can modify and
remove existing ACLs on a given file, but they cannot add new ones (that
can only be done with setfacl on the
(b) In said ACL properties dialog, the usernames displayed
are the UNIX ones, not the ones converted with the username
map option.
Why not use original Windows names and take users map out of the loop?
While a blank in user's name is strictly a no-no and all lower case is
preferable, most
(b) In said ACL properties dialog, the usernames displayed
are the UNIX ones, not the ones converted with the username
map option.
Why not use original Windows names and take users map out of the loop?
While a blank in user's name is strictly a no-no and all lower case is
preferable, most
