>> $ setfacl -m DOMAIN+andrewfu:rwx myfile
>> setfacl: Option -m: Invalid argument near character 1
>
I had a similar issue on my Debian box. It seemed that setfacl didn't
care for special characters. I changed the separator character to -
(dash) instead of + or \ and it worked fine.
It looks
(offlist replies discontinued due to increasing large number of people
involved)
Gareth Davies wrote:
> Shouldn't you be setting setfacl -m DOMAIN+andrewfu:rwx myfile ?
I tried that, but it didn't work:
setfacl: Option -m: Invalid argument near character 1
I also tried escaping/quoting the +
On Wed, Nov 27, 2002 at 12:08:12PM +0800 or thereabouts, Andrew Furey wrote:
> (recipient list getting longer...)
>
>
> >>Via username mapping, yes (we're a member server in a 2k mixed domain,
> >>but that side of things seems to be working).
> >>
> >>On further investigation, it appears that I
- Original Message -
From: "Andrew Furey" <[EMAIL PROTECTED]>
To: "David Pullman" <[EMAIL PROTECTED]>
Cc: "Anthony J. Breeds-Taurima" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, November 27, 2002 4:08 AM
Subject: Re:
Your w2k-client has to join the Windows-Domain.
I only tried this once with the Samba-Server being the domain's PDC and
a w2k-client being directly connected to it.
As long as the client had not joined the domain, I could not add users
which were generally known to the server but only change ACLs
On Wed, 27 Nov 2002 11:22:19 +0800
Andrew Furey <[EMAIL PROTECTED]> wrote:
> On further investigation, it appears that I _can_ modify existing
> ACLs, and I can even remove them (users, at least); but I can't add
> users to the ACL, which is what I really need.
Your w2k-client has to join the Win
(recipient list getting longer...)
Via username mapping, yes (we're a member server in a 2k mixed domain,
but that side of things seems to be working).
On further investigation, it appears that I _can_ modify existing
ACLs, and I can even remove them (users, at least); but I can't add
users
Andrew Furey wrote:
The problem arises when I try to change them from W2k. It silently
fails (from 2k's point of view), but in the log files I see
something like "unable to map SID [blah] to uid or gid".
>
Is the win2k user the owner (in the unix sense) of the file. ?
Even though you have
The problem arises when I try to change them from W2k. It silently fails
(from 2k's point of view), but in the log files I see something like
"unable to map SID [blah] to uid or gid".
>
Is the win2k user the owner (in the unix sense) of the file. ?
Even though you have ACL's only the owner or r
On Wed, 27 Nov 2002, Andrew Furey wrote:
> Hi all,
>
> I'm having trouble making Samba recognise ACLs properly - a W2k client
> isn't using them fully.
>
> I have patched the kernel, recompiled Samba, etc. I've gotten it working
> to the point where the kernel-side of things seems to work fi
Hi all,
I'm having trouble making Samba recognise ACLs properly - a W2k client
isn't using them fully.
I have patched the kernel, recompiled Samba, etc. I've gotten it working
to the point where the kernel-side of things seems to work fine (with
getfacl, etc). Also, the W2k machine (via Samba
11 matches
Mail list logo