search for: list_directory

...map system = no The zfs permissions I'm testing look like this. This is for the parent directory; files within have the same permissions (sans the inheritance). moe-lh /moe2/office/student_workers 546# ls -vd . drwxrws---+ 2 toml cefac 5 Oct 20 18:36 ./ 0:group:cefac:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/write_xattr/execute/write_attributes /write_acl/write_owner:file_inherit/dir_inherit/inherit_only:allow 1:group:cefac:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/write_xatt...

...not limited to a single user and single group. # ls -lvd /Pool1/Department/Sales drwxrwx---+ 13 jsmith sales 48 Nov 29 18:58 /Pool1/Department/Sales 0:user:nobody:read_xattr/read_attributes/read_acl:allow 1:user:root:read_xattr/read_attributes/read_acl:allow 2:group@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/read_xattr/write_xattr/execute/delete_child /read_attributes/write_attributes/delete/read_acl/write_acl /write_owner/synchronize:allow 3:owner@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/read_xattr...

There are definitely some files with some weird names- in an ssh session they don't even have regular characters. e.g -rw-rw---- 1 xxx xxx 114985112 Oct 31 14:39 ▒^t Not sure if that is related to problems though. The top command shows Memory: 12G phys mem, 343M free mem, 2048M total swap, 2048M free swap This is in the evening so should not be much load but I think

...ad & write access To do this I created the /Departments folder, and granted just the permissions shown. In windows it looks fine, and under Solaris it looks ok too, the permissions appear as: d---r-x---+ 3 ross smith domain users 3 Feb 28 08:24 Departments 0:group:domain admins:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/read_xattr/write_xattr/execute /delete_child/read_attributes/write_attributes/delete/read_acl /write_acl/write_owner/synchronize:file_inherit/dir_inherit:allow 1:group@:list_directory/read_data/read_xattr/execute/read...

...ven when posix permissions are set to 777. (see test5 below) Nexenta configuration ================= No specific workgroup No AD or LDAP configuration Acls on folder bigmirror/big: local users smb and nfs, owner@ have full access, everyone@ and group@ (root) are denied write access owner@ Allow:list_directory, read_data, add_file, write_data, add_subdirectory, append_data, write_xattr, execute, write_attributes, write_acl, write_owner group@ Allow:list_directory, read_data, execute Deny:add_file, write_data, add_subdirectory, append_data everyone@ Allow:list_directory, read_data, read_xat...

...177 Jan 18 14:58 /tmp/bob/test/ 0:user::rwx 1:group::rwx #effective:rwx 2:mask:rwx 3:other:r-x -bash-3.00# ls -lavd /zfs/internal/streams drwxrwsr-x 2 root NDS-UK\dept_stream_content 3 Jan 18 14:38 /zfs/internal/streams/ 0:owner@::deny 1:owner@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/write_xattr/execute/write_attributes/write_acl /write_owner:allow 2:group@::deny 3:group@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/execute:allow 4:everyone@:add_file/wri...

...except we deny the "write_acl" part. The ACLs are pretty much the defaults that happen with a normal chmod except for the write_acl part. It looks like this: chown root username chmod A- username chmod og-rwx username chmod A+user:username:write_acl:deny username chmod A+user:username:list_directory/read_data/add_file/write_data/add_subdirectory/append_data/read_xattr/write_xattr/execute/delete_child/read_attributes/read_acl/write_owner/synchronize:allow username chmod A+group@:read_xattr/read_attributes/read_acl/synchronize:allow username chmod A+everyone@:read_xattr/read_attributes/read_acl/...

Hi, this series cleans up the Python sources, either static or generated, including also tests, to make them PEP 8 compliant; see https://www.python.org/dev/peps/pep-0008/ and tools like pep8. Almost all the issues reported by pep8 are fixed, reducing the issues from 3818 to 7. The changes should have no effect on the actual code, while it will help Python users with consistency with other

Hi Karl, Thanks for your help, About the "Connection:" header, you are right, it's: "Connection: close" and NOT "Connection: keep-alive". The protocol when the SERVER sends the data is http 1.0. It's http 1.1 when the browser requests the data. I don't understand the "Content-Length: 54000000" header either. Also I noticed the flash player on