similar to: Resetting default permissions on share

On 8/24/2015 12:43 PM, Sébastien Le Ray wrote: > Hi > > setfacl -Rb /srv/samba/share > chown nobodycares:a group with SeDiskOperatorPriviledge /srv/samba/share > chmod g+rwx /srv/samba/share > > always did the trick for me > > Regards > > Le 24/08/2015 18:35, James a écrit : >> Hello, >> >> How do I reset default folder permissions? For

Hi setfacl -Rb /srv/samba/share chown nobodycares:a group with SeDiskOperatorPriviledge /srv/samba/share chmod g+rwx /srv/samba/share always did the trick for me Regards Le 24/08/2015 18:35, James a écrit : > Hello, > > How do I reset default folder permissions? For instance I have the > following in my smb.conf > > [share] > path = /srv/samba/share >

Don't know if this helps or not, but if the original permission were correct, how about just restoring them after re-creating the directory? I save both ATTRs and ACLs (perhaps the problem is that you're missing attr settings?) getfattr -dR /var/lib/samba/sysvol /var/lib/samba/share >/backupATTR.txt getfacl -R /var/lib/samba/sysvol /var/lib/samba/share > /backupACL.txt Or,

> > On the file serever: > > Collected config --- 2019-07-03-10:27 ----------- > > > > Hostname: srv > > DNS Domain: a.b.hu > > FQDN: srv.a.b.hu > > ipaddress: 10.0.3.15 192.168.0.8 > > ----------- > > Samba is running as a Unix domain member > > ----------- > > > > This computer is running Debian 10.0 x86_64 > >

Hi Rowland, Chown to Administrator seems less flexible than Chgrp to Domain Admins on the face of it. You could add/remove users from the Domain Admins group, which allows/denies them the ability to change the permissions on the share. By changing the owner to Administrator, only those credentials would have that ability, no? What advantages do you predict with the change owner approach? What

Hello all, Sorry about the top-posting. I have added the bit about the linking (YAY!, I'm helping!). Now if we can clear up the ACL issue, this will be a great day! Summary: To edit ACL's from Windows on a Debian Member server, we need to either 1) map the domain admin to root OR 2) give explicit permissions to Domain Admins with a chmod 0755 and chgrp "MYDOM\Domain Admins"

Hi Rowland, I'm also not an expert, but with the amount of help you provide on the list, I will defer to you. I'd love to know your rational for prefering the "change ownership to administrator" approach over the "change group to Domain Admins approach". If it's just gut, that's fine too! Thanks! -----Original Message----- From: samba-bounces at

On 2017-04-23 17:01, Rowland Penny wrote: > On Sun, 23 Apr 2017 14:07:44 +1000 > Henry via samba <samba at lists.samba.org> wrote: > >> Following: >> >> https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs >> >> In windows: >> >> I can set permissions under the "Share Permissions" tab. >> >> I am

On 25/10/2020 20:37, Sonic wrote: > The reset allowed the current GPO to take effect, but right after > adding a new GPO (just named it, no editing, or linking) the > sysvolcheck fails: > # samba-tool ntacl sysvolcheck > ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception > - ProvisioningError: DB ACL on GPO directory >

Hello again List, Marc, and Louis! I'm afraid my message from yesterday may have been TL;DR. The short version is as follows: Following the wiki's for AD member server (building from source on Debian Wheezy) and Setting up shares with Windows acls did not give the expected results First, I needed to link libnss_winbind.so to /usr/lib/x86_64-linux-gnu for winbind to work. Marc - may I

Hi All. Greetings from South Africa. I have a Samba LDAP server (v 3.022) running on Ubuntu 6.10 Its serving about 200 users, with profiles, and domain logons. I want to start server MS Access Databases on it, with the best speed performance as possible. At the moment, the back ends for these databases, are about 200+ MB, and will grow over the next few years. Basically, the share should

Hi there, I?ve been trying to get my head around a problem I have with Samba. I?ve set up Samba 3.6.13 on a Raspberry Pi with Arch Linux ARM on it and let it serve a couple of folders from an attached external ext4 drive mounted to /srv/cifs (of course with the "acl" option enabled). I?ve been trying to create a share that is read-writable for all members of a particular UNIX user

I suggest you start with : 1770 /server (+ creator owner ) 3770 /server/programs ( + creator owner + creator group. ) Then check again with getfacl Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Shmerykowsky via samba > Verzonden: dinsdag 19 februari 2019 23:13 > Aan: Rowland Penny > CC: samba at

Hello List! I have a Samba AD domain with two virtualized DC's running 4.1.15 and 4.1.17. I have had two member file servers with odd permissions problems that I've now given up on, and decided to start fresh. I have created a File server (FS3) with Debian wheezy, built samba 4.1.17 from source, with configure options of : --with-ads --with-shared-modules=idmap_ad ... and placed the

Thank you. Basically our problem are not the ACLs or their support per se, but that we have to manage a huge number of individual ACLS (several hundred users in more than hundred projects) in multi-petabyte filesystem and still have to keep overview and control. Our problem is more the management side. Effectively we are looking for a tool that helps us manage these permissions and we

On Fri, May 15, 2015 at 4:37 AM, Klaus Hartnegg <hartnegg at uni-freiburg.de> wrote: > Not sure which email you mean. I don't think that this can happen. If the > Linux acls are modified, the Windows ACLs are destroyed and all is based on > the Linux permissions and acls (which looks strange when viewed from > Window). If the Windows ACLs are modified, Samba automatically

> On Mon, 21 Nov 2016 13:42:57 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > >> Hi, >> >> Yes thats correct. >> But try the following. >> Make sure you use the usermapping. >> >> username map = /etc/samba/samba_usermapping >> containing: >> !root = NTDOM\Administrator NTDOM\administrator

Hi, I would like to set filesystem permissions on shares (users, at the moment) with Windows 10 (1809). On the Samba side, the filesystem is ext4. I tested the extended attributes usability with setfattr/getfattr, and setfacl/getfacl, and they work. I set the followings in smb.conf: [global] vfs objects = acl_xattr map acl inherit = yes store dos attributes = yes ... [users] path = /home/users

Hi Rowland, Thank you for the reply and info. On Tue, Jun 13, 2017 at 11:19 AM, Rowland Penny <rpenny at samba.org> wrote: > On Tue, 13 Jun 2017 09:15:40 +0200 > Neil via samba <samba at lists.samba.org> wrote: > > > OK, this a DC and therefore you will have to do things differently from > a Unix domain member. > > You might as well remove these lines from

Hello, After researching the subject on the internet I concluded that Samba should take into account Unix file acls. During my tests I found the opposite. Only Unix file mode bits are respected, and file acls are ignored. If my initial assumption is correct and Samba do respect Unix file acls, then I am doing something wrong. Please see the setup below and point to what I am doing wrong.