search for: setfacls

Displaying 20 results from an estimated 775 matches for "setfacls".

Did you mean: setfacl
2019 Jul 23
2
errors restoring samba
> Jul 22 14:39:39 dc1 named[27846]: samba_dlz: Failed to connect to > /var/lib/samba/private/dns/sam.ldb The good news is I believe I've found the problem: RUNNING: # file: samba/private # owner: root # group: root user::rwx group::r-x group:bind:r-x mask::r-x other::--- RESTORE: # file: samba/private # owner: root # group: root user::rwx group::r-x other::--- The bad news is
2014 Dec 18
6
setfacl: Option -m: Invalid argument near character 3
I just tried that and I got the same error. I think there is some extended acl support that I'm missing somewhere. It's like the setfacl command is not recognizing the AD groups as valid groups. I should also add the following information: This server is built up on CentOS 6.6 Minimal using the Sernet-Samba Enterprise packages. It looks like the binary that is running is
2014 Apr 11
1
sub-folders security access question
Hi Guys! A simple question.. I never worked with ACL's and since my costumer want some access levels for some sub-foldes in shares, I am reading some manuals about that.. But.. Before apply some testings, I need some advices about this.. Here is my question... Parent folder (share): FOLDER Sub-folder1: PROJETC1 Sub-folder2: PROJECT2 User1: DIRECTOR Group: Director/Projects User2: Employee1
2014 Dec 19
3
setfacl: Option -m: Invalid argument near character 3
On 19/12/14 13:22, Rich Webb wrote: > Matt, > > Thanks for the reply. I'm not trying to add the "users" group. I'm > trying to add the "Domain Users" group. That is the reason for the \ in > front of the space. It's translated as a literal. I think I could also > put quotes around it and not have to use the \ and the space. > > The
2014 Dec 19
2
setfacl: Option -m: Invalid argument near character 3
What's the content of your /etc/nsswitch.conf? Am 19. Dezember 2014 14:22:56 MEZ, schrieb Rich Webb <rwebb at zylatech.com>: >Matt, > >Thanks for the reply. I'm not trying to add the "users" group. I'm >trying to add the "Domain Users" group. That is the reason for the \ >in >front of the space. It's translated as a literal. I think
2010 Jan 12
2
setfacl:operation not supported
Hi all from last few days i got struct in problem.when i try to use setfacl command "setfacl -m u:himmat:r-- /ide2/asd" i get the error setfacl : /ide2/asd : operation not supported i also has mounted acl using -: "mount -f -o remount,acl / " Note: -f option is for force i am using red hat kernel 2.4.20-8 and acl-2.2.3-1 One more thing i have to ask whether acl utility
2014 Dec 19
3
setfacl: Option -m: Invalid argument near character 3
Im did not follow the complete thread, but you can check the following. smb.conf ## map id's outside to domain to tdb files. idmap config *:backend = tdb idmap config *:range = 50001-80000 ## map ids from the domain the range may not overlap ! idmap config DOMAIN:backend = ad idmap config DOMAIN:schema_mode = rfc2307 idmap config DOMAIN:range = 10000-40000 winbind
2014 Dec 18
2
setfacl: Option -m: Invalid argument near character 3
Hi, I have a Samba 4 AD DC running for which I now want to create a file share on it and control permissions through windows. I provisioned the domain with this command: samba-tool domain provision --use-rfc2307 --interactive --function-level=2008_R2 --use-ntvfs My share definition in my smb.conf is as follows: [Shared] comment = Shared Files path =
2014 Dec 19
3
setfacl: Option -m: Invalid argument near character 3
On 19/12/14 13:40, Rich Webb wrote: > Running CentOS 6.6 > Using the Sernet Enterprise packages - sernet-samba-ad. > > Just tried: > > getent group "Domain Users" > getent group DOMAIN\\Domain\ Users > > and neither command returned any entries. > > Rich > > -----Original Message----- > From: samba-bounces at lists.samba.org >
2014 Dec 19
0
setfacl: Option -m: Invalid argument near character 3
Matt, Thanks for the reply. I'm not trying to add the "users" group. I'm trying to add the "Domain Users" group. That is the reason for the \ in front of the space. It's translated as a literal. I think I could also put quotes around it and not have to use the \ and the space. The problem is getent group only is listing local unix groups. I think that is
2007 Aug 06
1
setfacl(1) - Can FreeBSD's ACLs contain groups from NT/AD domains ?
Hi all, I have "FreeBSD 7.0-CURRENT #1: Wed Jul 25" authenticating successfully against active directory via samba's winbindd(8). I need to manage samba shares via FreeBSD ACLs and CIFS ACLs. From my reading of setfacl(1) I should be able to set group permissions using the syntax of DOMAIN\group-name. For example: #setfacl -d -m g:"MYDOMAIN\mygroupname":rwx test
2014 Dec 19
1
setfacl: Option -m: Invalid argument near character 3
On 19/12/14 01:33, Rich Webb wrote: > Please is there anyone who has an answer on why this might be happening? > Do I need some sort of sssd support or winbind or something? In the > wiki about setting up acl's it doesn't say anything about any other > requirements, only that you have to have acl support and xattr support > in your filesystem which I do. > > I'm
2014 Dec 19
0
setfacl: Option -m: Invalid argument near character 3
Running CentOS 6.6 Using the Sernet Enterprise packages - sernet-samba-ad. Just tried: getent group "Domain Users" getent group DOMAIN\\Domain\ Users and neither command returned any entries. Rich -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny Sent: Friday, December 19, 2014 8:37 AM To: samba
2010 May 18
3
[PATCH] btrfs: should add a permission check for setfacl
On btrfs, do the following ------------------ # su user1 # cd btrfs-part/ # touch aaa # getfacl aaa # file: aaa # owner: user1 # group: user1 user::rw- group::rw- other::r-- # su user2 # cd btrfs-part/ # setfacl -m u::rwx aaa # getfacl aaa # file: aaa # owner: user1 # group: user1 user::rwx <- successed to setfacl group::rw- other::r-- ------------------ but we
2004 Nov 22
1
setfacl fails for some user names and not others
Hi I'm currently using Samba 3.0.4 with LDAP as a PDC. The PDC is in a trusted relationship (both ways) with a Windows NT4 server. I tried updating to 3.0.7 a short while back but had problems using 'setfacl' to set permissions for users on the trusted domain - i.e. > setfacl -m u:remote-dom+jbloggs:r-x . setfacl: Option -m: Invalid argument near character 3 Setting
2014 Dec 19
0
setfacl: Option -m: Invalid argument near character 3
The only thing I have in my smb.conf that is related is this: idmap_ldb:use rfc2307 = yes I don't have any of that other stuff for mapping ids. Is there a howto on that somewhere? and my nsswitch.conf I have: passwd: files sss shadow: files group: files sss the sss was only because I was trying sss but it was ONLY "files" to start with. Rich -----Original
2014 Dec 20
0
setfacl: Option -m: Invalid argument near character 3
I also have two DCs and I am using them also as filers. Built-In users and groups are normally mapped by idmap.ldb I also got issues with mapping of built-in users. I needed the same idmap.ldb on both of my DCs. I also don't see these groups by hitting getent group. I followed another stragedy: Every new group that will have filesystem access has a name starting with GGF (Group Global File).
2018 Feb 02
2
Samba 4.6.2 does not inherit setgid bit (anymore)
thanks for suggestion, in other words you use only ACLs for users denying all for groups, unfortunately we had many group such as domain users, secretary, finance, etc belonging to users for which we need to apply at least 770 in order to gain a simplified permission management using groups the actual dirty workaround I applied was to track new files/dir by tailing with follow ( tail -f ) a
2015 Mar 20
1
Centos 6: setfacl: .: Argument list too long
On 20.03.2015 02:14, muiz wrote: > Dear all, > > > I have a Centos 6 (64bit) server used for samba and ACL control. > There has a folder which a lot of user can access, when I add a new user's ACL, but failed, do you know how to resolve this problem? use xargs like in: |find . -name "*.pdf" -print0 | xargs -0 RUNACOMMAND robert | > > > [root at s1
2014 Dec 19
0
setfacl: Option -m: Invalid argument near character 3
Please is there anyone who has an answer on why this might be happening? Do I need some sort of sssd support or winbind or something? In the wiki about setting up acl's it doesn't say anything about any other requirements, only that you have to have acl support and xattr support in your filesystem which I do. I'm trying to deploy this server and I need a working solution tomorrow -