search for: acl_set_fil

...rms rwx [2012/07/03 17:19:29.724979, 10] smbd/posix_acls.c:2757(set_canon_ace_list) canon_ace index 4. Type = allow SID = S-1-5-21-1177087545-3838858134-2882343936-1117 uid 10000 (rshen) SMB_ACL_USER ace_flags = 0x0 perms rwx [2012/07/03 17:19:29.725214, 10] modules/vfs_posixacl.c:91(posixacl_sys_acl_set_file) Calling acl_set_file: NeoSphere/test100.txt, 0 [2012/07/03 17:19:29.725260, 10] modules/vfs_posixacl.c:110(posixacl_sys_acl_set_file) acl_set_file failed: Operation not supported [2012/07/03 17:19:29.725300, 2] smbd/posix_acls.c:2828(set_canon_ace_list) set_canon_ace_list: sys_acl_set_file...

...he level 10 logging and then connecting via Computer Management from a 2003 server on the AD domain to the already joined Linux/Samba box. Then I tried to set permissions first on the Bldgshare share and followed by the Public share. Following are the only errors/failures I saw. log.evrt-dc1: acl_set_file failed: Operation not permitted log.evrt-dc1: set_canon_ace_list: sys_acl_set_file type file failed for file . (Operation not permitted). log.evrt-dc1: set_nt_acl: failed to set file acl on file . (Operation not permitted). log.evrt-dc1: acl_set_file failed: Operation not permitted log.evrt-d...

...om_sbuf) dos_mode_from_sbuf returning d [2011/05/26 15:27:02.144615, 8] smbd/dosmode.c:666(dos_mode) dos_mode returning d [2011/05/26 15:27:02.144659, 3] smbd/dosmode.c:166(unix_mode) unix_mode(test-dir) returning 0775 [2011/05/26 15:27:02.144710, 10] modules/vfs_posixacl.c:89 (posixacl_sys_acl_set_file) Calling acl_set_file: test-dir, 0 [2011/05/26 15:27:02.144762, 10] modules/vfs_posixacl.c:108 (posixacl_sys_acl_set_file) acl_set_file failed: Operation not permitted [2011/05/26 15:27:02.144815, 10] smbd/open.c:3381(create_file_default) create_file: access_mask = 0x2 file_attributes = 0x0,...

...efault permissions for new files in a folder that take the place of the `umask'. This option should be a matter of getting the ACL on one system using "acl_get_file" and "acl_copy_ext", sending it to the other system, and applying it using "acl_copy_int" and "acl_set_file". It would take a little more work to preserve IDs by name and make this play nicely with "--numeric-ids". The "-a" option should probably include "--acl". -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this...

...access, too. If you only access the data via Samba you might set this to yes to achieve better NT ACL compatibility. From the description, I thought if I set it to yes it will skip/ignore the setting of system ACL and only store NT ACL in xattr. However, the error still appear in Samba log: acl_set_file failed: Operation not supported even after I set it to yes. Following is my share definition: [test] vfs objects = acl_xattr acl_xattr: ignore system acls = yes available = yes path = /mnt/ceph/test browseable = yes read only = no guest ok = no create mask = 0644 directory mask = 0755 valid user...

Maybe I'm doing somthing really stupid, but while copying some windows share onto a samba server, on some random subdirectory robocopy says ERROR 87 (0x00000057) Copying NTFS Security to Destination Directory... The samba logfile has lots of these lines. modules/vfs_posixacl.c:349(smb_acl_to_posix) smb_acl_to_posix: ACL is invalid for set (Das Argument ist ung?ltig) The strange thing is

Hi, I am using kernel 3.7-rc6. I have written a test application for extended attributes and have for some folders a wired behaviour: #include <stdio.h> #include <string.h> #include <attr/xattr.h> char attrs[1024]; ssize_t attrslen; int i; char value[1024]; ssize_t valuelen; int main(int argc, char *argv[]) { if (argc != 2) { fprintf(stderr, "Syntax: testxattr

..._xattr' vfs_find_backend_entry called for acl_xattr Successfully loaded vfs module [acl_xattr] with the new modules system Initialising custom vfs hooks from [dfs_samba4] vfs_find_backend_entry called for dfs_samba4 Successfully loaded vfs module [dfs_samba4] with the new modules system Calling acl_set_file: /usr/local/samba/var/locks/sysvol/tmpoEPBWP, 0 set_conn_connectpath: service (null), connectpath = / Initialising default vfs hooks Initialising custom vfs hooks from [/[Default VFS]/] vfs_find_backend_entry called for /[Default VFS]/ Successfully loaded vfs module [/[Default VFS]/] with the new...

Split up the huge generator/actions.ml into several smaller files. Rich.

This is a follow-up to the other generator changes in: https://www.redhat.com/archives/libguestfs/2017-February/msg00217.html Rich.

...g (Pathname, "path"); String (PlainString, "acltype")], []; optional = Some "acl"; shortdesc = "get the POSIX ACL attached to a file"; longdesc = "\ @@ -8171,7 +8171,7 @@ C<path> is a directory. { defaults with name = "acl_set_file"; added = (1, 19, 63); - style = RErr, [Pathname "path"; String "acltype"; String "acl"], []; + style = RErr, [String (Pathname, "path"); String (PlainString, "acltype"); String (PlainString, "acl")], []; optional = Some &...

Very large but mechanical change to the generator. Rich.

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..0943bf305 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-M UI,

The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...