similar to: acl_xattr vs acl_tdb

Hi, I had issues using"vfs objects = acl_xattr" (possibly too old version [Version 4.13.13-Debian] for the needed "acl_xattr:security_acl_name = user.samba" option needed if running in a non-priv container). So I tried "vfs objects = acl_tdb" and found it working. In https://wiki.samba.org/index.php/File_System_Support I found: File systems without xattr support

My organization is in the position of having to support full Windows ACLs on CIFS shares. We've been successfully utilizing Samba 3.5.10-125 and vfs_acl_tdb to accomplish that. However, the size of the resulting /var/lib/samba/state/file_ntacls.tdb[.unique-extension] file(s) has introduced some new problems for me to solve. In our environment, it seems on average each stored ACL causes

Hello, When I am using module acl_tdb and I am trying to get access to directory I am getting call trace in log.ip Best regards! /Adrian Berlin =============================================================== [2010/03/24 13:54:05.295901, 0] lib/fault.c:47(fault_report) INTERNAL ERROR: Signal 11 in pid 15556 (3.5.1) Please read the Trouble-Shooting section of the Samba3-HOWTO [2010/03/24

Hello all I am now experimenting with samba 3.3.0 and acl_xattr. I can see that there is another method of storing Windows ACLs: acl_tdb. Can someone here tell me something about the relative merits and demerits of those two methods? I am using CenttOS with an ext3 filesystem. Thank you!

Hi, i have a running samba+ctdb installation with samba as a domain-member. everything works but the acl's. The users want to be able to set permissions on the share. glusterfs does not support extended acls, so i am using acl_xattr. xattr is installed and i can manually set attributes using setfattr on the shared-directory. if i try to set the permissions using a winxp client i'll get a

yes i have, this is my share-config: [share] path = /mnt/gluster/daten/share/ public = yes writeable = yes browseable = yes inherit permissions = Yes inherit acls = Yes map acl inherit = Yes nt acl support = yes vfs objects = acl_xattr F?bio Leandro Rodrigues Cordeiro schrieb: > Hi, > > Have you tried adding the share writeable? > [share] > writeable = yes > > att, >

Hello, How to manage acl from command line when using acl_tdb module?

Hello, What is simplest way to backup/restore acl's if using acl_tdb module? Thanks.

We are using SAMBA 3.6.6 on Centos 5 with the acl_tdb VFS module. Our share is backed by storage on a SAN devices that does not support ACLs or extended attributes ... so we're trying the acl_tdb module as a mechanism to support Windows ACLs. We have verified that samba has ACL support enabled, and ACL support works find if we export the share from the local EXT4 filesystem. When trying to

Hi Michael, On Thu, Aug 18, 2016 at 11:42:12AM +0200, Michael Adam wrote: > From reading the original post, I get the impression > that the problem is associated to the share root directory. nope. It will happen with just any directory or file created from a non SMB client, eg mkdir|touch (or NFS, ...) on the server. It is also associated with files or directories created from Windows

Hello, Does anyone test ZFS on Linux and ACLs? I can't setup POSIX ACLs and any extended even using acl_xattr or acl_tdb. Is any way to use ACLs with ZFS on Linux (Samba 3 or 4)? Best regards /Adrian Berlin --

On 30.01.2024 16:51, Ralph Boehme via samba wrote: > On 1/30/24 16:27, Rowland Penny via samba wrote: >> On Tue, 30 Jan 2024 16:13:41 +0100 >> Peter Milesson via samba <samba at lists.samba.org> wrote: >> >>> Hi folks, >>> >>> It seems that the setting acl_xattr:ignore system acls = yes reduces >>> Windows compatibility when defined

On Fri, Aug 26, 2016 at 06:33:26PM +0200, Ralph Böhme via samba wrote: > On Thu, Aug 25, 2016 at 12:14:00PM -0700, Jeremy Allison wrote: > > On Wed, Aug 24, 2016 at 04:06:42PM +0200, Ralph Böhme via samba wrote: > > > > > > Yeah, as much as I'd like to avoid adding a new option, I guess we > > > have to do something about it, my latest take on this is >

On 1/30/24 16:27, Rowland Penny via samba wrote: > On Tue, 30 Jan 2024 16:13:41 +0100 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> Hi folks, >> >> It seems that the setting acl_xattr:ignore system acls = yes reduces >> Windows compatibility when defined for a share. In all attempts I >> have used Windows tools (except editing

On Fri, Aug 26, 2016 at 04:03:49PM -0700, Jeremy Allison wrote: > On Fri, Aug 26, 2016 at 02:46:19PM -0700, Jeremy Allison via samba wrote: > > On Fri, Aug 26, 2016 at 06:44:05PM +0200, Ralph Böhme wrote: > > > > > > Cheerio! > > > -slow > > > > Still reviewing this - but a few things that will need changing: > > > > When adding the

Hi! I have few question to developers of VFS ACL modules (acl_tdb and acl_xattr): 1. Do you plan to extend quantity of entries in acl_tdb (now I can write 22 user ACLs plus CREATOR OWNER, CREATOR GROUP, domain users and everyone) 2. Do you plan to fix few ACLs eg. Traverse folder / Execute file (to traverse I need to enable additional permission List folder / read data to traverse through

On 08/18/2016 08:28 AM, Ralph Böhme wrote: > Hi Eric, > > On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: >> I was testing Samba 4.5rc2 with an existing smb.conf file that I have been >> using since Samba 4.1.x and found that I cannot access data in the share on >> Windows 2012 (my AD server), a Windows 2008 client or on a Ubuntu 16.04 >>

I often get the message: EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2 I have googled for a reason and a way to solve this - but not found something I could use. Maybe somebody here konws what to do? best regards keld

I get the following warning when running xend start, and a similar warning sometimes when doing xm commands: /usr/lib/python/xen/xend/XendNode.py:26: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xc: This Python has API version 1012, module xen.lowlevel.xc has version 1011. import xen.lowlevel.xc /usr/lib/python/xen/xend/xenstore/xstransact.py:10: RuntimeWarning:

Suse 10.1 AMD64 Xen3 New to Xen. The dom0 is up and running. I am trying to get my first domU working. My approach is to use precompiled images from jailtime.org. After some manual tinkering with the .cfg file the domU proceeds to boot but stalls with the following error. I cannot get past this - any ideas ? Brian Using config file "/etc/xen/vm/vm1". Started domain vm1 Bootdata ok