search for: namesspace

...mmm. This has been changed for Samba 4.8.0 and above, > with commit df99ac27106dededcf0a98a251e58c24b90bf6d1. > > This would seem to be a correct fix, as it seems > > "The "system" xattr namespace is reserved for the kernel. Any attempt to > use xattrs in that namesspace will fail with EOPNOTSUPP, regardless of > priveleges." > > Can you check with 4.8.x ? I guess that statement may not be correct, depending on which kernel subsystem exposes the xattr? My testing was with local filesytems, not with nfsv4 mounts. Apparantly it works with nfs4_get...

Hi All I found there is one bug in the plugin. The name of the attribute for ACL as per strace output of nfs4_setfacl is *system.nfs4_acl.* The source code has defined it as #define NFS4ACL_XATTR_NAME ( "system.nfs4acl" ) Note there is missing underscore. After this, the EOPNOTSUPP error is not observed. Hope this helps Akash On Thu, Apr 5, 2018 at 11:43 PM, Jeremy Allison

...> > Hope this helps Hmmm. This has been changed for Samba 4.8.0 and above, with commit df99ac27106dededcf0a98a251e58c24b90bf6d1. This would seem to be a correct fix, as it seems "The "system" xattr namespace is reserved for the kernel. Any attempt to use xattrs in that namesspace will fail with EOPNOTSUPP, regardless of priveleges." Can you check with 4.8.x ? Jeremy. Author: Ralph Boehme <slow at samba.org> Date: Thu Nov 2 12:17:48 2017 +0100 librpc/idl: rename NFS4 ACL xattr name The "system" xattr namespace is reserved for the k...

...gt; > with commit df99ac27106dededcf0a98a251e58c24b90bf6d1. > > > > > > This would seem to be a correct fix, as it seems > > > > > > "The "system" xattr namespace is reserved for the kernel. Any attempt to > > > use xattrs in that namesspace will fail with EOPNOTSUPP, regardless of > > > priveleges." > > > > > > Can you check with 4.8.x ? > > > > I guess that statement may not be correct, depending on which kernel subsystem > > exposes the xattr? My testing was with local filesyte...

...Samba 4.8.0 and above, > > with commit df99ac27106dededcf0a98a251e58c24b90bf6d1. > > > > This would seem to be a correct fix, as it seems > > > > "The "system" xattr namespace is reserved for the kernel. Any attempt to > > use xattrs in that namesspace will fail with EOPNOTSUPP, regardless of > > priveleges." > > > > Can you check with 4.8.x ? > > I guess that statement may not be correct, depending on which kernel subsystem > exposes the xattr? My testing was with local filesytems, not with nfsv4 > mounts...

...ac27106dededcf0a98a251e58c24b90bf6d1. > > > > > > > > This would seem to be a correct fix, as it seems > > > > > > > > "The "system" xattr namespace is reserved for the kernel. Any attempt to > > > > use xattrs in that namesspace will fail with EOPNOTSUPP, regardless of > > > > priveleges." > > > > > > > > Can you check with 4.8.x ? > > > > > > I guess that statement may not be correct, depending on which kernel subsystem > > > exposes the xattr? My t...

...one defines an Axis.MyClass outside of the 'graphics' namespace, it is called automatically by 2.6.2 on objects of MyClass, i.e. R would search for further method definition outside of the graphics namespace. Looks like this behaviour has changed in 2.7.0 so that UseMethod called in a given namesspace (graphics) does not despatch on methods defined in another namespace (global or another package) as the example below shows. Have I done something wrong? Is it an intended behaviour, any idea how to go around it? Thanks, Oleg PS: The difference in the code below is that 2.6.2 calls Axis.MyClass...

Hello Timo and everyone, I think on such an idea that may save me a bit of space and time: in my company we have a mailbox that holds a copy of every message that our SMTP processed. While it eats a lot of space, it saved us several times when, you may imaging, user "suddenly" deleted the most important message in his life and call our IT guys for help. The mailbox contains

...b90bf6d1. > > > > > > > > > > This would seem to be a correct fix, as it seems > > > > > > > > > > "The "system" xattr namespace is reserved for the kernel. Any > attempt to > > > > > use xattrs in that namesspace will fail with EOPNOTSUPP, > regardless of > > > > > priveleges." > > > > > > > > > > Can you check with 4.8.x ? > > > > > > > > I guess that statement may not be correct, depending on which kernel > subsystem >...